How can we help?

[Preview] Talkdesk Voyager: Use Cases
Published • Last Updated

Preview: This feature is available in Preview for select customers.

This article presents six use cases for Talkdesk Voyager™. Each use case describes the business context, the flow, the capabilities used, and the business value.

Table of Contents

Abandoned Chat Reengagement

This use case shows how Talkdesk Voyager turns an abandoned web chat into an automated, intent-based follow-up.

Understanding the Business Context

A shopper opens a web chat to ask about a membership — box sizes, delivery days, and pricing — and then closes the chat without signing up. The interest was real, but the moment passed.

Abandoned chats like this are common, and without a timely, personal follow-up, the intent they contain is lost. In this use case, a Voyager assesses the intent shown in the conversation and then follows up automatically on the right channel with the right message.

Reviewing the Voyager at a Glance

  1. A web chat ends without a sign-up.
  2. The Voyager assesses the intent from the conversation.
  3. If the intent is high, the Voyager waits three minutes and then places an AI voice call.
  4. If the call confirms intent, the Voyager sends a personalized SMS with a discount code and ends.
  5. If the contact is no longer interested, the Voyager sends a warm closing SMS and ends.
  6. If the call is not answered, the Voyager ends.
  7. If the assessed intent is none, the Voyager sends a fallback SMS with an opt-in prompt and ends.

Understanding How the Voyager Works

  1. Entry — the chat interaction ends. The Voyager starts when the web chat interaction ends without a sign-up. The conversation context — what the shopper asked about — carries into the Voyager as Voyager variables.
  2. Intent assessment. The Voyager analyzes the conversation and routes on the result:
  • High intent: The shopper asked multiple specific questions, which signals genuine interest.
  • No intent: The shopper showed little engagement.
  1. High intent — AI voice call after a short wait. The Voyager waits three minutes, and then an AI Voice Call continues the conversation and reassesses intent:
  • Intent confirmed: The Voyager sends a personalized SMS with a discount code and ends. 
    • Example: "Hi Alex, great speaking with you! Here's 15% off your first Fresh Box — code FRESH15, valid for 24 hours: freshbox.com/signup".
  • No longer interested: The Voyager sends a warm closing SMS and ends. Example: "Hi Alex, no worries at all! Whenever you're ready, we'd love to welcome you. freshbox.com".
  • No answer on call: The Voyager ends.
  1. No intent — fallback SMS. The Voyager sends a low-key opt-in message and ends. Example: "Thanks for reaching out! Whenever you're ready, we're here. Reply Y to get exclusive deals and updates."

Identifying Key Capabilities

This use case relies on the following capabilities:

  • Entry from a chat interaction: The Voyager starts when the web chat interaction ends, with conversation context carried in as Voyager variables.
  • AI interaction assessment: An AI step analyzes the conversation and routes the Voyager based on the assessed intent (high or none).
  • Wait: A three-minute wait keeps the AI Voice Call timely without feeling intrusive.
  • AI Voice Call: An outbound AI voice step continues the conversation and reassesses intent, with outcomes routing the Voyager.
  • SMS outreach: Personalized messages (name and discount code) serve as the follow-up and fallback touchpoints.
  • Conditional routing: Clear, named branches cover each intent and call outcome, with a defined end for every path.

Understanding the Business Value

This use case delivers the following benefits:

  • Fast recovery of high-intent visitors: A three-minute follow-up on the most personal channel (voice) reaches shoppers while their interest is still warm.
  • Low-cost path for low-intent visitors: A single opt-in SMS keeps the door open without investing call effort where there is no interest.
  • No dead ends: Every path closes with a personalized offer, a warm farewell, or a quiet end.
  • Consistent automation: The follow-up runs the same way every time, with no manual triage of abandoned chats.

Batch Campaign: Regional SMS at 10,000 to 100,000 Contacts

This use case shows how Talkdesk Voyager runs a regional SMS campaign for a large contact list as one Voyager.

Understanding the Business Context

A regional SMS campaign is simple until it runs at scale. Ten thousand contacts spread across cities usually means splitting the list by region by hand, building a separate campaign per city, and keeping each message variant in sync. At 10,000 to 100,000 contacts, the manual work outgrows the campaign itself.

In this use case, a single CSV upload feeds one Voyager that routes each contact to the message for their city and keeps a fallback path for numbers that match no region.

Reviewing the Voyager at a Glance

  1. 10,001 contacts enter through a single CSV upload.
  2. A condition routes each contact by phone area code.
  3. Area code 212 (New York) receives the NYC summer promo SMS (3,334 contacts).
  4. Area code 312 (Chicago) receives the CHI summer promo SMS (3,333 contacts).
  5. Area code 310 (Los Angeles) receives the LA summer promo SMS (3,333 contacts).
  6. A number with no match (the one Oakland number) receives a fallback SMS with a generic offer, which doubles as the end-to-end delivery check.

Understanding How Voyager Works

  1. Entry — one CSV upload. The FitNation marketing team uploads all 10,001 contacts in a single CSV. A data source node reads the file and makes each contact, including the phone number, available to the Voyager.
  2. Routing by area code. A condition node routes each contact by phone area code:
  • 212: New York (3,334 contacts).
  • 312: Chicago (3,333 contacts).
  • 310: Los Angeles (3,333 contacts).
  1. A message for each city. Every branch sends its regional offer:
  • NYC summer promo: Times Square opening, free seven-day pass.
  • CHI summer promo: Lakefront Running Club, 50% off the first month.
  • LA summer promo: Sunset Yoga Series, free training session.
  1. Fallback for unmatched numbers. One number, with an area code that does not match any city, takes the fallback branch and receives an SMS with a generic offer. Its successful delivery confirms that the pipeline works end to end.

The result is 10,001 messages sent with no manual splitting and no separate campaigns.

 

Identifying Key Capabilities

This use case relies on the following capabilities:

  • Data source node (file): A single CSV upload brings all 10,001 contacts into the Voyager.
  • Conditional routing: One condition node routes every contact by phone area code, with a default branch for unmatched numbers.
  • SMS outreach: Each regional branch sends its own offer, so one Voyager carries four message variants.
  • Fallback path: Unmatched numbers still receive a message, which doubles as an end-to-end delivery check.
  • Batch scale: The same Voyager design holds from 10,000 to 100,000 contacts, with no redesign as the list grows.

Understanding the Business Value

This use case delivers the following benefits:

  • No manual splitting: The list goes in as one file, and the Voyager segments it by region.
  • No separate campaigns: One Voyager provides one place to edit and one report to read. Adding a city means adding a branch, not a campaign.
  • Built-in pipeline check: The fallback branch confirms that messages flow end to end, so a silent list or routing problem surfaces as a message instead of a mystery.
  • Scale: The same design serves lists from 10,000 to 100,000 contacts.

 

Preference-Driven Outreach: Right Channel, Right Time, Right Language

This use case shows how a single Talkdesk Voyager reaches each contact on a preferred channel, at a local time, and in a preferred language.

Understanding the Business Context

An EU outreach team runs campaigns across Spain, Portugal, Germany, and France. Every market is different: some customers answer a call, and some respond to an SMS. Each country has its own language, and every contact has a daily rhythm and time zone. The traditional approach builds one campaign per country per channel — four lists, four schedules, and four message sets, all maintained by hand.

In this use case, one contact list feeds a single Voyager, and every contact is reached on their own channel, in their own language, at their own local time.

Reviewing the Voyager at a Glance

One contact list covering four countries enters the Voyager. The Voyager reads the preferences of each contact and splits into two paths:

  1. The Voyager starts from its trigger and runs once on the contact list.
  2. A condition reads the preferred channel of each contact and routes the contact to the voice path or the SMS path.
  3. On the voice path, the Voyager waits for the timezone-adjusted window of the contact, matches the language of the contact to the voice prompt, and places an automated voice call.
  4. On the SMS path, the Voyager waits for the window, matches the language to the SMS template, and sends the SMS.
  5. SMS replies go into a follow-up step. If a contact does not reply within 24 hours, the Voyager ends.

Understanding How the Voyager Works

  1. One list, one run. The team uploads a single contact list covering Spain, Portugal, Germany, and France. The Voyager runs once against the whole list, with no manual splitting by country or channel.
  2. The Voyager decides per contact. For each contact, the Voyager reads the preferred channel from the contact data and routes the contact to voice or SMS. The decision is made per profile, not per campaign.
  3. Each contact waits for a window. Before anything goes out, both paths hold the contact at a timezone-adjusted wait. For example, Maria in Spain receives a Spanish voice call between 8:00 AM and 10:00 AM, Ana in Portugal receives a Portuguese SMS at 6:00 PM Western European Time (WET), Hans in Germany receives a German voice call at 8:00 PM, and Pierre in France receives a French SMS at 12:00 PM. The same Voyager produces a different path for every contact.
  4. Language follows the contact. The voice path matches the language of the contact to the voice prompt, and the SMS path matches it to the message template. No separate content per market needs maintenance.
  5. Replies get a follow-up, and silence closes the Voyager. SMS recipients who reply move into a follow-up step. Contacts who stay silent for 24 hours end the Voyager, which confirms that the per-contact branching holds end to end.

Identifying Key Capabilities

This use case relies on the following capabilities:

  • Audience (contact list): One list covering four countries runs the Voyager in a single pass.
  • Condition node: Routes each contact to the voice path or the SMS path based on the preferred channel.
  • Wait node (timezone-adjusted): Holds each contact until the local contact window, which provides per-contact timing instead of per-campaign timing.
  • Personalized content: Matches voice prompts and SMS templates to the language of each contact (Spanish, Portuguese, German, and French).
  • Automated voice call: Delivers the localized voice message on the voice path.
  • SMS with reply follow-up: Sends the localized SMS, routes replies into a follow-up step, and closes the Voyager after 24 hours without a reply.

Understanding the Business Value

This use case delivers the following benefits:

  • One Voyager: Four countries, two channels, and four languages run from one list, with no manual splitting and no per-market campaign maintenance.
  • Per-contact precision at list scale: Channel, language, and timing are decided per profile, so every contact receives the version of the outreach that fits.
  • Respect for the contact window: Timezone-adjusted waits prevent messages from going out at the wrong local hour, which supports better answer rates and fewer complaints.
  • No dead ends: Replies continue into a follow-up step, and silence ends the Voyager cleanly.

 

Sidecar Sub-Journeys: Real-Time Parallel Actions During a Live Call

This use case shows how a Talkdesk Voyager sidecar sends an SMS while an AI voice call is still in progress.

Understanding the Business Context

A customer showed interest in the Fresh Box membership on the website but never signed up. FreshMart's AI voice agent, Sage, calls to re-engage the lead. On a normal call, the agent can only talk. If the customer asks about pricing or the nearest store, the agent describes the answer and relies on the customer to remember it. The information that the customer wants most arrives only as speech, at the pace of the call.

In this use case, a sidecar turns that single-voice moment into a talk-and-text experience. While Sage introduces the product on the call, a matching SMS arrives on the customer's phone at the same moment, so the customer can listen and read at once.

Reviewing the Voyager at a Glance

  1. The main Voyager places an AI voice call that re-engages a website lead with the Fresh Box introduction.
  2. Mid-call, the agent detects a price or location intent.
  3. A sidecar — a sub-journey that runs inside the main Voyager — fires and runs in parallel.
  4. The sidecar sends an SMS with the matching detail: the pricing sheet or the store address. The SMS is independent of the call outcome.
  5. The call continues uninterrupted and then ends.
  6. The outcome assessment of the Voyager classifies the call and selects the exit.

Understanding How the Voyager Works

  1. The call starts with a Voyager. Sage, the FreshMart AI voice agent, calls the website lead and introduces the Fresh Box membership. The main Voyager is the call itself.
  2. The agent detects intent mid-call. While discussing the details, Sage detects a price or location intent, such as the customer asking about cost or the nearest store.
  3. The sidecar fires in parallel. Instead of interrupting the call, the Voyager fires a sidecar, which is a sub-journey that runs inside the main Voyager. The sidecar sends an SMS with the matching detail: the pricing sheet for the quarter or the Washington-area store addresses.
  4. Talk and text happen in the same live moment. The call continues uninterrupted while the SMS arrives. The customer listens to Sage and reads the pricing or store details on the phone at once.
  5. The call ends, and the Voyager assesses. When the call finishes, the outcome assessment classifies the call and selects the exit. The sidecar SMS is independent of the call outcome, so the information is already with the customer either way.

Identifying Key Capabilities

This use case relies on the following capabilities:

  • AI Voice Call: Sage re-engages the website lead and introduces the Fresh Box membership.
  • Intent detection: Detects a price or location question while the call is live.
  • Sidecar (sub-journey): Runs in parallel inside the main Voyager, triggered by the detected intent.
  • SMS: Delivers the pricing sheet or store address while the call is still in progress.
  • Outcome assessment: After the call, the Voyager classifies the call result and routes to the right exit.

Understanding the Business Value

This use case delivers the following benefits:

  • Talk and text in the same live moment: The customer hears the pitch and sees the details at once, in one coordinated interaction instead of two separate ones.
  • An uninterrupted call: The sidecar answers the customer's question without interrupting the conversation.
  • Information independent of call outcome: Whether the call converts, ends early, or drops, the pricing or store detail is already delivered.
  • One Voyager, two channels, no handoffs: The main Voyager and the sidecar run inside the same Voyager, with no separate campaign and no manual coordination between systems.

 

Event-Filtered Follow-Up: Automatic SMS When a Contact Declines a Call

This use case shows how a Talkdesk Voyager event filter sends a follow-up SMS only when a contact declines a call.

Understanding the Business Context

An agent, or an AI Voice Voyager, places an outbound call to a contact. The contact declines immediately, likely because the contact is busy. Normally, the interaction ends there. A declined call is a dead end, and nobody has time to call back or send a manual "sorry I missed you" message.

A call produces many outcomes: Answered, declined, no-answer, and missed. A follow-up that triggers on any outcome is worse than none, because it would message people who just had a full conversation. The team needs precise control over which outcome triggers a follow-up.

In this use case, a Voyager subscribes directly to a related event and applies an event filter. The Voyager reacts only to the outcome that matters, here a declined call, and sends the follow-up automatically.

Reviewing the Voyager at a Glance

  1. An agent or an AI voice Voyager places an outbound call from the Contact app.
  2. The contact declines the call (likely busy), and the call ends immediately.
  3. A Talkdesk internal event fires and carries the call outcome: declined.
  4. The event filter of the Voyager matches, targeting "declined" only.
  5. The follow-up fires: an SMS that explains why the contact was called.

Understanding How the Voyager Works

  1. The call is placed from the Contact app. An agent dials the contact, or an AI Voice Voyager places the call. No Voyager setup is required on the caller side.
  2. The contact declines. The call ends immediately. On its own, nothing happens next.
  3. The internal event fires. The call outcome (declined) is emitted as a Talkdesk internal event, alongside all the other call outcomes.
  4. The event filter does the work. The Voyager subscribes to that related event and applies an event filter that targets "declined" only. A no-answer or missed connection passes by without triggering anything.
  5. The follow-up goes out automatically. When the filtered event matches, the Voyager sends a follow-up SMS that explains why the contact was called, with no further action from the agent.

Identifying Key Capabilities

This use case relies on the following capabilities:

  • Related event trigger: The Voyager subscribes directly to a Talkdesk internal event instead of starting the interaction itself.
  • Event filter: Restricts the reaction to one event type among many. In this case, "declined" only, not no-answer or missed.
  • SMS: Delivers the follow-up that explains why the contact was called.
  • No agent-side effort: The agent or AI Voice Voyager places the call as usual, and the follow-up requires no further action.

Understanding the Business Value

This use case delivers the following benefits:

  • Precise control over follow-ups: The Voyager reacts to exactly one outcome type among many, instead of triggering on any call outcome.
  • Second chances instead of dead ends: A declined call, previously the end of the interaction, becomes a timely and relevant follow-up.
  • No agent workload: The SMS explains why the contact was called, and agents keep working their queues.
  • Works with any caller: The behavior is the same whether a human agent or an AI Voice Voyager placed the call.

 

Per-Recipient Email Attachments: Personalized Documents for Every Member, in One Send

This use case shows how a single Talkdesk Voyager send delivers each member their own documents as email attachments.

Understanding the Business Context

A fitness center sends every member their membership and billing documents each week or month. Each pack is unique: A membership summary and a billing statement for that member. Done by hand, someone has to match the right PDFs to the right person and send hundreds of individual emails, which is slow, tedious, and prone to attaching the wrong file to the wrong member.

In this use case, one Voyager covers the entire membership in a single send. Every member receives exactly their own two documents, membership and billing, attached correctly, with no manual matching. Each cycle runs again with a fresh list, and nothing needs to be rebuilt.

Reviewing the Voyager at a Glance

The flow has two halves: a data preparation step on the customer side once per cycle, and the Voyager that turns the prepared data into a single batch send.

Preparing the Data (Customer Side)

  1. Upload the PDFs of each member to secure storage, and read back the metadata of each attachment.
  2. Prepare a CSV that contains the member list plus the attachment metadata and storage references.

Running the Voyager

  1. The Voyager reads the CSV, with one row per member.
  2. The variables of the Voyager are configured to map the CSV columns, including the attachment references.
  3. The email step binds to the right variables, with one message template plus the attachments of each member.
  4. The Voyager sends one batch, and every member receives their own two PDFs.

Understanding How the Voyager Works

  1. The documents are staged once per cycle. The fitness center uploads the PDFs of each member to secure storage and prepares a CSV with one row per member, carrying the member list plus the references to the attachments for that member.
  2. The CSV drives the Voyager. A data source node reads the prepared file into the Voyager, and every row becomes the run of one member.
  3. Variables carry the links. The variables of the Voyager are configured to map the CSV columns, including the attachment references, so the row of each member identifies where the two documents of that member are stored.
  4. The email binds to the right variables. The email outreach step uses one message template for everyone and binds the attachments to the variables of each member: the membership summary of that member and the billing statement of that member.
  5. One batch send delivers every pack correctly. The Voyager sends one email per member with their own two PDFs attached. The email template is the same for everyone, and the per-recipient attachments are resolved automatically. For the next cycle, load the fresh list and run the Voyager again.

Identifying Key Capabilities

This use case relies on the following capabilities:

  • Data source (file): Reads the prepared CSV into the Voyager, so that one row per member drives one personalized email.
  • Voyager variables: Carry the data of each member through the Voyager, including the references to the attachment documents of that member.
  • Email with attachments: Sends one email per member with the membership and billing PDFs of that member, resolved per recipient.
  • Batch send: One send covers the entire membership list, with no per-member manual emails.
  • Re-runnable by cycle: Each week or month, a fresh list runs through the same Voyager, and nothing needs to be rebuilt.

Understanding the Business Value

This use case delivers the following benefits:

  • One send instead of hundreds of emails: A single batch Voyager run covers the entire membership, and each member receives their own document pack.
  • No manual matching: Attachment references travel with the row of each member in the CSV, so the right file reaches the right person and the risk of sending the wrong file is removed.
  • One template, many packs: The email content is identical for everyone, and only the attachments are per recipient, which keeps maintenance simple.
  • Ready for the next cycle: Each run needs only a fresh list, and the Voyager itself never changes.

 

Additional Resources

  • Overview: For more information, see Talkdesk Voyager: Overview in this article.
  • How-to: For instructions, see Talkdesk Voyager: Building and Publishing a Voyager in this article.
  • Reference: See Talkdesk Voyager: Configuring Audiences and Entry Points in this article.
All Articles ""
Please sign in to submit a request.

Related to