Vianordis
--:--:-- UTCVianordis / SUPPORT
marketing

Voxia

Beta

Voxia is the campaign workspace for newsletters, announcements, and automated email journeys. Marketing and communications teams can manage audiences, build templates, schedule sends, and review engagement while respecting consent and unsubscribe requirements.

Open Voxia
Beta operating manual

Voxia beta campaign manual

Manage consented audiences and operate enabled email-campaign workflows in the current Voxia beta.

Manual
Version 1.0
Product
Voxia UI 0.1.0 beta
Verified
July 15, 2026
Language
English · Source
Owner
Voxia product and support
Source
voxia · 2b875b5
Review cycle
45 days
Start here

Audience, scope, and prerequisites

Covers the current beta’s list-management surface and campaign, template, automation, analytics, and compliance capabilities only when a functioning tenant route exposes them. The verified UI revision implements Dashboard and Lists; several dashboard quick links target absent routes.

Who this is for

  • Email marketing operators
  • Campaign reviewers
  • Privacy and tenant administrators

Before you sign in

  • A documented lawful basis and consent model
  • An approved sending domain and brand identity
  • A reviewed audience source and suppression process
  • A campaign approver separate from the final send action when required
Access model

Roles and responsibilities

RoleAccessResponsibilities
Audience operatorManage enabled lists and subscriber records.
  • Preserve consent evidence
  • Honor suppression and unsubscribe state
Campaign editorPrepare templates, segments, campaigns, and automations when exposed.
  • Use approved content and links
  • Send tests before scheduling
Approver or administratorApprove sends and review compliance or tenant configuration.
  • Verify audience, timing, domain, and legal requirements
  • Investigate complaints
Workspace map

Navigation

Dashboard

/{locale}

Open beta totals and quick actions; current totals are placeholder zero values.

Lists

/{locale}/lists

Review contact lists through the implemented UI route.

Campaigns

Not implemented in verified UI

Use only when a later tenant release exposes a functioning route.

Templates

Not implemented in verified UI

Use only when enabled and reviewed.

Analytics

Not implemented in verified UI

Use API-backed analytics only through an approved interface.

Chapter 01

Manage audiences and consent

A deliverable email address is not permission to send; each subscriber must have traceable status and lawful purpose.

Procedure 1.1

Review a contact list

Confirm ownership, purpose, consent, and current subscriber state before campaign use.

  1. 1
    Open Lists

    Use the implemented list route and search for the intended audience.

  2. 2
    Confirm list identity

    Check name, owner, business purpose, source, and expected size.

  3. 3
    Review subscriber status

    Account for active, pending, unsubscribed, bounced, complained, and suppressed records.

  4. 4
    Resolve unexpected data

    Do not send while list source, consent, or tenant ownership is unclear.

  5. 5
    Record campaign eligibility

    Document the approved segment and exclusions.

Expected result

The operator has a bounded, consented audience with understood exclusions and no cross-tenant records.

Procedure 1.2

Import or add subscribers when enabled

Use a reviewed source and retain consent provenance.

  1. 1
    Validate the source

    Remove prohibited fields, duplicates, malformed addresses, and records without lawful basis.

  2. 2
    Choose the correct list

    Confirm tenant, purpose, and double-opt-in settings.

  3. 3
    Map fields

    Map email, name, locale, consent time/source, tags, and required custom fields.

  4. 4
    Run a small test

    Import a bounded sample when the interface supports preview or validation.

  5. 5
    Review outcomes

    Reconcile created, updated, skipped, invalid, suppressed, and pending records.

Expected result

Imported subscribers retain provenance and correct status without reactivating suppressed or unsubscribed recipients.

Chapter 02

Prepare and send campaigns when enabled

The backend defines campaign, template, automation, and analytics capabilities, but the verified beta UI does not yet expose their routes.

Procedure 2.1

Prepare and approve a campaign

Proceed only through a functioning tenant interface approved for campaign use.

Before you begin

  • A functioning Campaigns and Templates route in the deployed release
  1. 1
    Select audience and exclusions

    Use the reviewed list or segment and current suppression state.

  2. 2
    Select an approved template

    Review subject, preheader, sender identity, body, links, tracking, and unsubscribe behavior.

  3. 3
    Render and test

    Send a test to the approved internal recipients and check desktop, mobile, plain-text, links, personalization, and footer.

  4. 4
    Review compliance

    Confirm sender domain, consent, targeting, timing, tracking, and required legal text.

  5. 5
    Approve exact version

    Freeze the audience, content, and schedule presented to the approver.

Expected result

An exact campaign version has an approved audience, tested rendering, working unsubscribe path, and documented send decision.

Procedure 2.2

Send or schedule and review results

Start one authorized send and monitor delivery and complaint signals.

  1. 1
    Reconfirm schedule

    Verify time zone, audience snapshot, sender, and approval immediately before action.

  2. 2
    Send once

    Use Schedule or Send and record the campaign identifier.

  3. 3
    Monitor status

    Watch queued, sending, sent, failed, bounced, complained, and unsubscribed counts.

  4. 4
    Stop unsafe follow-up

    Do not duplicate a campaign because status appears slow or stuck.

  5. 5
    Review analytics proportionately

    Use aggregate opens and clicks as directional signals; account for privacy protections and automated clients.

Expected result

One campaign completes with traceable delivery state, honored suppressions, and documented follow-up.

Operating rules

Security and data handling

  • Preserve consent, unsubscribe, complaint, and suppression evidence.
  • Use an approved sending domain and least-privileged campaign roles.
  • Never send from placeholder dashboard data or an unreviewed generated template.
  • Treat recipient lists, segments, exports, and engagement data as personal data.
  • Require human approval before activation of campaigns or automations.
Current release

Known limitations

Read before relying on an unsupported workflow

These limits describe the source-pinned Voxia UI 0.1.0 beta scope and must be rechecked when the product changes.

  • Only Dashboard and Lists routes are implemented in the verified UI revision.
  • Dashboard totals are hard-coded zero placeholders rather than live analytics.
  • Campaign, template, analytics, and automation components and APIs do not prove an end-user route is available.
  • Some AI template-generation code uses mock generation when no provider is supplied.
  • All send, tracking, compliance, and integration behavior requires tenant-level acceptance.
Problem solving

Troubleshooting

You cannot sign in to Voxia

Likely cause: The session expired, the identity is not assigned to the application, or the tenant claim is missing.

  1. Open the application from the approved portal and complete sign-in again.
  2. Confirm that the correct organizational identity and tenant are selected.
  3. If access is still denied, record the time and request an entitlement check from support.

A documented action or navigation item is not visible

Likely cause: The current role, release, tenant configuration, or feature flag does not expose that operation.

  1. Confirm the role and prerequisites listed for the procedure.
  2. Reload the page after signing in again; do not attempt to bypass the interface through direct URLs.
  3. Ask the product owner whether the feature is enabled for the tenant before reporting a defect.

A saved change or background operation is not visible

Likely cause: Validation failed, processing is still running, or the current view is stale or filtered.

  1. Review inline validation, status indicators, filters, and the selected tenant or workspace.
  2. Refresh once and search for the item by its stable name or identifier.
  3. Do not repeat irreversible or externally visible actions until the original operation status is known.

A dashboard action opens a missing route

Likely cause: The quick link targets a capability not wired into the current beta UI.

  1. Return to Dashboard or Lists.
  2. Record the locale, action, and resulting path.
  3. Do not invoke campaign APIs directly unless an approved operator procedure exists.

A campaign appears stuck in sending

Likely cause: Workers, SMTP delivery, queue state, or status updates are delayed or failed.

  1. Do not create a duplicate send.
  2. Record the campaign ID and current counts.
  3. Have an operator inspect queue and worker state before any retry.
Escalation

Contact support

Contact support when

  • A repeatable Voxia error blocks an approved workflow
  • Expected data, permissions, or tenant boundaries appear incorrect
  • A security, privacy, compliance, or data-loss concern is suspected
  • A recipient was contacted without valid consent
  • Suppressed recipients appear active
  • A campaign may have been submitted more than once

Include

  • The page, action, and expected result
  • The exact error text and time of occurrence, including time zone
  • Your tenant, role, browser, and a sanitized record or item identifier
  • Whether the problem can be reproduced and which troubleshooting steps were tried

Never include

  • Passwords, access tokens, API keys, recovery codes, or session cookies
  • Unredacted personal, health, financial, or other regulated data
  • Private encryption keys or complete confidential documents unless an approved channel is provided
Contact support