> ## Documentation Index
> Fetch the complete documentation index at: https://developer.zeckta.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Reporting FAQ

> Frequently asked questions about message tracking, campaign reports, delivery status monitoring, and analytics.

<AccordionGroup>
  <Accordion title="How can I track an SMS after sending it?" icon="magnifying-glass">
    Use the Message Status endpoint.

    ```http theme={null}
    GET /v1/messaging/sms/messages/{messageId}
    ```

    This endpoint returns the latest delivery status and message metadata.
  </Accordion>

  <Accordion title="How can I receive delivery updates automatically?" icon="webhook">
    Configure a callback URL when sending a message or campaign.

    Zeckta will deliver real-time webhook events as message statuses change.

    Supported events include:

    * MESSAGE\_SUBMITTED
    * MESSAGE\_SENT
    * MESSAGE\_DELIVERED
    * MESSAGE\_FAILED
    * MESSAGE\_UNDELIVERABLE
    * MESSAGE\_EXPIRED
    * MESSAGE\_REJECTED
  </Accordion>

  <Accordion title="What is the difference between polling and webhooks?" icon="arrows-rotate">
    Polling requires your application to repeatedly query the Message Status API.

    Webhooks push delivery updates directly to your application as events occur.

    For production workloads, webhooks are generally recommended.
  </Accordion>

  <Accordion title="How can I retrieve a campaign report?" icon="chart-column">
    Use the Campaign Report endpoint.

    ```http theme={null}
    GET /v1/messaging/sms/campaigns/{campaignId}
    ```

    Campaign reports provide delivery statistics and message-level results.
  </Accordion>

  <Accordion title="What information is available in a campaign report?" icon="file-lines">
    Campaign reports include:

    * Campaign details
    * Recipient count
    * Message statistics
    * Delivery totals
    * Failed message counts
    * Paginated message results
  </Accordion>

  <Accordion title="What delivery metrics are available?" icon="signal">
    Campaign reports may include:

    * Queued
    * Sending
    * Sent
    * Delivered
    * Failed

    These metrics help track campaign performance and delivery progress.
  </Accordion>

  <Accordion title="Can I see individual message results within a campaign?" icon="list">
    Yes.

    Campaign reports include paginated message results that allow you to inspect individual recipients and message identifiers.
  </Accordion>

  <Accordion title="How long does it take for delivery reports to appear?" icon="clock">
    Delivery reporting depends on downstream carrier processing.

    Messages may transition through several statuses before reaching a final state.

    Examples:

    * QUEUED
    * PROCESSING
    * SUBMITTED
    * SENT
    * DELIVERED
  </Accordion>

  <Accordion title="What are final delivery states?" icon="flag-checkered">
    A message reaches a final state when no further status changes are expected.

    Examples include:

    * DELIVERED
    * FAILED
    * UNDELIVERABLE
    * EXPIRED
    * REJECTED
  </Accordion>

  <Accordion title="Can I track OTP delivery?" icon="shield">
    OTP requests return a session identifier that can be used during verification.

    OTP workflows focus on verification status rather than delivery reporting.
  </Accordion>

  <Accordion title="Why is a message still marked as QUEUED?" icon="hourglass-half">
    A queued status indicates the message has been accepted and is waiting for processing.

    This is typically temporary before progressing to:

    * PROCESSING
    * SUBMITTED
    * SENT
  </Accordion>

  <Accordion title="Can campaign statistics change over time?" icon="chart-line">
    Yes.

    As delivery receipts arrive from carrier networks, campaign statistics may continue to update until all messages reach a final state.
  </Accordion>

  <Accordion title="Can another workspace view my reports?" icon="building">
    No.

    Reports, messages, campaigns, sender names, and OTP sessions are isolated by workspace.

    Cross-workspace access is not permitted.
  </Accordion>
</AccordionGroup>