Outbound data overview

After a call ends, Sprio can push data into your connected systems — a CRM lead update, a call log, a support ticket, a WhatsApp message, an email — depending on which integrations you've connected. Every outbound push runs through the same engine, so the concepts on this page apply across LeadSquared, Zoho CRM, Zoho Desk, WhatsApp, and Email, even though each integration's actual payload looks different (see Payloads for the per-integration specifics).

When a push fires

Two settings control whether an outbound push happens for a given call:

1. Call status filter — which call outcomes qualify, e.g. only completed and transferred calls, excluding no_answer or failed calls entirely. Configured per integration.

2. Run condition — an optional additional filter evaluated against the call's extracted data, metadata, or duration. A push only fires if the condition passes. Supported operators:

   Operator	Checks
   equals / not_equals	Exact match against a field's value
   in	Field's value is one of a configured list
   not_empty	Field has any non-blank value
   any_not_empty	At least one of several named fields has a value
   less_than / greater_than	Numeric comparison (e.g. call duration)
   or combinator	Any one of several sub-conditions passes

   For example, Zoho Desk's default run condition only creates a ticket when extracted lead_intent is in ["complaint", "support_request", "callback"] — a routine informational call never creates a ticket.

If neither filter is configured, every call in a completed/transferred state produces a push — this is a real volume consideration worth confirming with a client before enabling an integration broadly.

How field values are built

Every outbound field (a CRM field, a ticket property, an email body) is defined by a payload map — a per-field rule describing where its value comes from: a literal, a call property, an AI-extracted field, a template string, or something more dynamic like a value lookup or a conditional branch. See Payload map reference for the full list of source types and what each is for.

Timing: immediate vs. deferred

Most pushes happen as soon as the call ends. Some integrations (Email/SMTP) support deferred send — the content is computed and held, then actually sent once the call fully completes, so the send can reflect the final call outcome rather than a mid-call snapshot. See Integration: Email (SMTP).

Failure behavior

Outbound pushes are best-effort by default — a failure doesn't retroactively undo anything that already succeeded (e.g. a ticket that was created stays created even if attaching the recording to it fails afterward). See Retries and failures for exactly what retries automatically, what doesn't, and where to check outcomes.

Where to check what actually happened

Integrations → Activity on each connection is the authoritative record — it shows every attempted push, whether it succeeded, and why it was skipped or failed. This matters because a push can be legitimately skipped (run condition didn't match, call status excluded) without that being an error — don't assume "no CRM update" means something broke.