Connect Consio to Omnisend to track customer calls, call outcomes, and orders attributed to Consio interactions. You can use this activity to create event-based segments and trigger Omnisend Automation Workflows for follow-ups, post-sale nurturing, win-back campaigns, and order-related messaging.
Note: This is a one-way integration. Data flows from Consio to Omnisend, and Omnisend does not send data back to Consio.
What The Integration Tracks
The integration sends three events to Omnisend. You can enable each event individually and use them as triggers in Automation Workflows.
Call Completed
This event is sent when a call reaches a final state in Consio. This includes:
Answered or connected calls
Missed calls
Voicemails
Invalid numbers
The event can include the call status, direction, duration, disposition, and customer identity when available.
Call Logged
This event is sent when an agent or Consio’s AI submits a disposition for a call, such as CLOSED_SALE, NOT_INTERESTED, or FOLLOW_UP_NEEDED.
Call Logged can be sent at the same time as Call Completed or later. If it is sent later, both events appear as separate entries on the contact timeline.
Order Attributed
This event is sent when Consio determines that a Shopify order resulted from a call, voicemail, or SMS interaction.
Not every interaction qualifies for attribution. Consio only attributes revenue to:
A connected call, meaning the call was answered.
A voicemail left during an outbound call, meaning the merchant or agent called the customer and left a voicemail. A voicemail left on an inbound call, such as when a customer calls, and nobody answers, does not qualify.
An SMS exchange that includes both an inbound and an outbound message.
An unanswered inbound call does not qualify for attribution on its own, regardless of how the call is dispositioned.
The event can include:
Order total and currency
Product line items
Financial and fulfillment status
Campaign name, when applicable
The call or interaction linked to the order
Note: Product line item details, such as titles, SKUs, and product or variant IDs, may not always be included in this event. This depends on the data Consio provides, which the integration cannot currently guarantee for every order.
Order Attributed is a Custom Event, not a native Omnisend order. It will not appear in Omnisend’s Sales Reports, Dashboard Overview, or “Revenue from Omnisend” figures. These reports use native order data from your store’s direct Shopify connection. Order Attributed’s order total and product data are available for Automation Workflows and message personalization, not for Omnisend’s built-in revenue reporting.
The default attribution window is:
Seven days for calls
One day for voicemails
Seven days for SMS interactions
You can configure these attribution windows in Consio under Settings → Attribution.
The integration does not create standalone SMS events. SMS interactions are supported only when Consio attributes an order to them.
Before You Begin
Make sure you can:
Access the relevant Consio workspace
Create an API key in Consio
Access the Consio integration in Omnisend
Set Up The Consio Integration
In Consio, go to Settings → API keys.
Click Create API key.
Copy the API key immediately. Consio displays it only once. The key starts with
csk_.In Omnisend, open the Consio integration.
Enter your Consio workspace name. You can find your workspace name in the Consio URL. For example, in
app.consio.ai/acme/..., the workspace name isacme.Paste the Consio API key.
Test the connection.
Enable the events you want to send to Omnisend:
Consio → Omnisend: Call completed
Consio → Omnisend: Call logged (disposition)
Consio → Omnisend: Order attributed
Important Notes:
You can enable any combination of these events. You do not need to enable all three. You can later use the enabled events as triggers in Automation Workflows.
After you enable the integration, Omnisend automatically registers to receive real-time updates from Consio. No additional manual setup is required.
Only the new activity is tracked. Calls and orders from before the integration was enabled do not appear retroactively.
What Data is Passed to Omnisend
When a customer has a completed call, a logged disposition, and a later attributed order, you’ll see three separate custom events on the same contact timeline:
Consio - Call completed
Consio - Call logged
Consio - Order attributed
Each event includes the properties available for that specific interaction. For example, a call event may include:
Call ID
Direction, such as inbound or outbound
Duration
Status
Disposition
Trigger type
An Order Attributed event may include the order total, currency, product information, financial status, fulfillment status, campaign name, and linked call ID. Properties that do not apply are omitted rather than shown as empty.
Call Disposition Values
The following disposition values were available during testing:
CLOSED_SALE, FOLLOW_UP_NEEDED, ALREADY_PURCHASED, NO_ANSWER, HUNG_UP, VOICEMAIL_LEFT, ERROR_LEAVING_VOICEMAIL, INVALID_NUMBER, NOT_INTERESTED, REMOVED_FROM_CAMPAIGN, DO_NOT_CALL, ISSUE_RESOLVED, WARM_LEAD, SPAM, FORWARDED_TO_NUMBER, and OTHER.
Consio may add or change disposition values over time. New or unrecognized values are passed to Omnisend as provided and do not cause an integration error.
Contact Identification & Marketing Consent
Consio’s call data typically includes a phone number rather than an email address. Omnisend can identify or create a contact using either a phone number or an email address.
As a result, a contact created from a phone call may show No name and no email address. This is expected when the person has only been identified by phone. The contact may be updated later if the customer provides an email address through an order, Signup Form, or another source.
Contacts created through this integration are not automatically subscribed to Email Campaigns or SMS marketing. You must capture separate, valid consent before sending marketing messages.
Use Consio Events in Omnisend
You can use event properties, such as `direction` and `disposition`, to control which contacts enter an Automation Workflow.
For example, you can:
Send a follow-up SMS or email after a missed call, voicemail, or no-answer disposition.
Send a thank-you or cross-sell message after an attributed order.
Create a win-back Automation Workflow for contacts with a
NOT_INTERESTEDdisposition.Create separate Automation Workflows for inbound and outbound calls.
Trigger an Automation Workflow only for selected dispositions instead of every call.
Note: Event properties, such as disposition, order total, or product titles, only work inside an Automation Workflow that uses the specific Consio event as its trigger. They cannot be used to filter contacts in a Segment. Segments can only check whether a Consio event has occurred at all, not filter by the event’s specific values. If you need audience-wide segmentation by something like disposition or order value, that data would need to live on the contact’s profile as a Custom Property instead, which this integration does not currently write.
Limitations and Expected Behavior
A single call can generate multiple events. Call Completed and Call Logged may appear as separate entries on the contact timeline.
An Order Attributed event may appear several days after the original call because attribution is processed within Consio’s configured attribution window.
Only qualifying interactions are attributed: a connected call, a voicemail left during an outbound call, or a two-way SMS exchange. An unanswered inbound call does not qualify, even if it reaches voicemail.
Not every call includes complete customer information. Missed calls, invalid numbers, and other interactions may contain limited identity data.
The integration tracks call-based events and attributed orders. It does not send standalone SMS events.
Contacts created through the integration are not automatically subscribed to marketing channels.
Historical calls and orders from before setup are not imported.
FAQ
Why does a contact show “No name” or no email?
The contact was identified using a phone number from a call. This is normal and does not indicate missing integration data.
I placed an order, but I don’t see an Order Attributed event. What should I check?
Attribution may take time to process in Consio. Confirm that:
The order was placed after the relevant interaction.
The customer’s phone number in Shopify matches the number used for the call.
The order falls within Consio’s configured attribution window.
The interaction qualifies for attribution.
Only a connected call, a voicemail left during an outbound call, or a two-way SMS exchange can be attributed. An inbound call that simply goes unanswered does not qualify, even if it is sent to voicemail. No order will be attributed to it.
Consio matches attribution using phone or email identity.
Can I filter which dispositions trigger an Automation Workflow?
Yes. Disposition is included as an event property, so you can configure workflow filters for specific values, such as NOT_INTERESTED or CLOSED_SALE.
Does the integration support outbound calls?
Yes. Both inbound and outbound calls are supported. The direction property identifies whether the call was inbound or outbound.
Why do I see two events for one call?
Call Completed and Call Logged are separate events. Call Completed is sent when the call reaches a final state, while Call Logged is sent when an agent or Consio’s AI submits a disposition. The events may be sent at different times.
Need help? If you have questions about connecting Consio to Omnisend, contact our Support team via in-app chat or at [email protected].