Skip to main content

Channels

Channels is where you turn each communication channel on or off and configure how the channel-specific behavior works — WhatsApp voice calls, how voice calls are processed, and the full set of email rules.

All sections appear in one continuous page with clear headings. Use the sticky On this page links to jump to a section. Each link adds a section fragment to the URL, so you can copy or bookmark the link and open that section directly. Save changes applies edits across the whole page; Discard restores the saved values. Changes are not saved automatically.

The page is organized into Channel availability, Email, and Voice calls.

Use the link icon beside a setting name to share that specific setting: click it and copy the browser address, or right-click and choose Copy link address. See sharing settings links for details.

Channel availability​

Communication channels​

Enable or disable each channel your team answers on. Turning a channel off stops Flowcall from handling conversations on it.

  • WhatsApp
  • Email
  • Live Chat
  • Instagram
  • Voice Call

Email​

Configure how inbound email is turned into tickets and how the AI replies. These options apply to your connected email inbox.

AI replies & handoff​

  • Enable automatic email replies — let the AI reply to incoming emails.
  • Require AI resolution check — suppress the AI reply and hand the ticket to an agent when AI cannot resolve it.
  • Passive analysis — analyze incoming emails without sending AI replies. The reply composer is hidden in Mails and customer email views while this setting is on. The AI still creates a ticket and tags its task, but never hands it to an agent: each ticket is resolved by AI after its email is analyzed, even when the task still needs details. A later email on the same thread adds what it learns to that ticket.
  • Max AI Email Replies — cap AI replies per email thread (0–10).

Incoming email & ticket creation​

Treat non-blacklisted domains as whitelisted controls whether other domains are treated as allowed. Blacklisted domains remain excluded.

Include Gmail spam — off by default. Turn it on when real customer emails land in your Gmail Spam folder, for example when another tool that reads the same mailbox shows emails Flowcall doesn't. Flowcall then also syncs emails Gmail marked as spam, from the moment you turn it on; earlier spam is not imported. Those emails go through the same address and domain rules below as any other email. Trash is never synced. This setting has no effect on Outlook mailboxes.

Merge split email threads — off by default. See Merging split email threads.

Each of these accepts multiple entries — type a value and press Enter to add it.

  • Alias Emails — addresses that belong to you. They're treated as your own and excluded from external-email filtering, so mail to or from them isn't mistaken for a customer.
  • Forwarded Email Sources — addresses that forward mail into this inbox, or aliases such as a grievance address that deliver to it. Mail from them is treated as an incoming customer email source rather than as the forwarder. Each source has its own options:
    • CC on agent and AI replies — copy the source on replies in conversations it is part of.
    • Always create a ticket for an agent — an email that involves this source skips the AI and goes straight to an agent. This also applies to a customer's reply on a thread whose earlier ticket is already closed; a reply while a ticket is still open joins that ticket.
    • Tell the customer it is being assigned to an agent — off by default. When off, the customer gets no automated handoff email for this source, including when the AI detects an escalation. When on, the customer gets the Assignment Message, or a short built-in note if none is set.
    • Default team — the team used when task and disposition routing have not picked one.
  • Blacklisted Domains — domains that should never create tickets. Mail from these domains is ignored even when Treat non-blacklisted domains as whitelisted is on. Addresses at these domains also never receive AI replies or CSAT surveys.
  • Force Create Ticket Emails — addresses that always create a support ticket, regardless of the other rules above.

Merging split email threads​

A customer's reply sometimes arrives as a new email thread instead of joining the one it answers. This happens when they reply to an email your mailbox never received, such as an automatic acknowledgement sent from another support tool, or when their mail app starts a new thread. Each thread would otherwise get its own ticket, be counted twice in thread and ticket reports, and be audited twice.

With Merge split email threads on, Flowcall checks every new email thread when it syncs your mailbox. If the thread continues one of the same customer's earlier threads, Flowcall merges the two:

  • The earlier thread's messages move into the new thread, so the new thread shows the whole conversation in order and the AI reads all of it.
  • The earlier thread's ticket moves to the new thread, so the reply is handled as if it had arrived on the earlier thread. The ticket's activity log records the merge.
  • The earlier thread disappears from Mails, the customer's email list and the email thread counts on the dashboard. Links to it open the new thread.
  • Conversation audits treat the merged threads as one conversation, so it isn't audited twice.
  • Later emails on the earlier thread are added to the new thread.

On the next analysis after a merge, Flowcall rebuilds the conversation summary from the combined messages in order. Later emails update that running summary while retaining material original faults, unresolved requests, and escalation history, alongside the latest developments. A short follow-up or a choice of warranty service does not by itself mean the earlier complaint is resolved.

Only new threads are merged, from the moment you turn the setting on. Threads synced before that stay as they are.

Flowcall treats a new thread as a continuation when one of these is true, checked in this order:

  1. Reply headers — the new email says it replies to an email in one of your other threads.
  2. Subject — the subject starts with a reply prefix such as Re: or Fwd:, and the same sender has an earlier thread with the same subject once the prefixes are removed. An empty subject or (no subject) never matches.
  3. Duplicate send — when Merge duplicate sends is on, the subject has no reply prefix, but the same sender sent an email with the same subject and the same opening text within the resend window.

Settings, shown once the setting is on:

  • Time window — the longest gap, in hours, between the earlier thread's last email and the new email (1–720, default 72).
  • Match on reply headers and Match on subject — turn each check on or off. Both are on by default.
  • Reply prefixes — the prefixes that mark a reply, without the colon. The defaults are re, fwd, fw and aw. Add the prefixes your customers' mail apps use in other languages.
  • Generic subject threshold — a subject that more than this many customers sent in the last 7 days is generic, for example a reply to one of your template emails. The default is 5.
  • Generic subjects — Merge only if the earlier email is quoted (default) merges a generic subject only when the new email quotes the customer's earlier email. Never merge keeps generic subjects apart.
  • Always treat as generic and Never treat as generic — subjects to override the automatic detection.
  • Merge duplicate sends and Resend window — off by default; the window is in minutes (1–1440, default 60).

Example​

A customer replies to your Shopify order confirmation: "When will my order arrive?". Your support tool sends an automatic acknowledgement, and the customer replies to it two minutes later: "How do I track my order?". Because the acknowledgement never reached your mailbox, the second reply opens a new thread. With the setting on, Flowcall moves the first reply into the new thread, so both messages are in one thread with one ticket.

Outgoing messages​

  • Assignment Message — hidden until you click + Add message. The text sent to the customer when their email is assigned to an agent. Leave it unset to send nothing on assignment.
  • Email Signature — the team or company name appended to outgoing email.
  • Email footer — text appended to outgoing Gmail and Outlook messages, including manual and AI replies, excluding CSAT emails. Supports plain text and simple HTTP/HTTPS links. Leave blank to disable.

How it works​

The domain and address lists are checked together when a new email arrives. Force Create Ticket Emails always wins and creates a ticket. Blacklisted Domains are dropped even when non-whitelisted ticket creation is enabled. Alias Emails and Forwarded Email Sources tell Flowcall which addresses are yours or are forwarders, so the real customer is identified correctly. Once a ticket exists, Enable automatic email replies and Max AI Email Replies govern whether and how many times the AI answers before handing off.

Voice calls​

WhatsApp voice calls​

Controls whether calls are allowed over WhatsApp.

  • Allow incoming calls — let customers place voice calls to you over WhatsApp.
  • Allow outgoing calls — let your team place voice calls to customers over WhatsApp.

Voice call processing​

This card appears only when the Voice Call channel is enabled. If it is disabled, use Go to channel availability to find the channel toggle, then save your changes. It controls how voice calls are transcribed, assigned, and resolved.

  • Minimum Call Duration — a length in seconds (0–3600). Calls shorter than this are ignored — not transcribed or processed. Use it to filter out accidental or dropped calls.
  • Auto-resolve call tickets — allow a processed call ticket to resolve automatically, but only when its inferred task is complete and no child ticket is pending. Turning this off leaves processed call tickets open for an agent.
  • Assign incomplete call tickets to the answering agent — after transcript processing, directly assign an incomplete parent task to the agent who answered the call. This setting is off by default and does not override the assignment flow for child tickets.
  • AI follow-up for details missed on the call — when a call ticket's task still needs information from the customer, including photos or documents, the AI asks for it over WhatsApp and email and continues the ticket where the customer replies. See Following up on details the call missed. On by default for accounts created after this feature launched; off for existing accounts until you turn it on.

How transcript-created tickets are assigned​

When a valid transcript creates a new call ticket, Flowcall records the answering agent as the ticket's preferred agent and runs the normal new-ticket distributor. The answering agent receives it when they are available, have capacity, and meet the ticket's channel and team/tag requirements. Otherwise, the distributor can assign another eligible agent or leave the ticket queued. This initial preference is independent of Assign incomplete call tickets to the answering agent.

After the transcript is analyzed, that setting controls only an additional direct reassignment. For this decision, a task is complete when Flowcall identifies the task and finds no remaining objectives. An incomplete parent task has an identified task with remaining objectives and has not created a child ticket.

SettingResult of transcript processingTranscript-driven assignment action
OffAny resultDo not reassign. Keep the existing assignment, or the result of normal new-ticket distribution.
OnIncomplete parent task, with no child ticketAssign or reassign the parent ticket directly to the answering agent. This can replace its current assignee.
OnIncomplete task that creates a child ticketDo not reassign the parent. The child ticket follows the task's configured team and assignment flow.
OnTask completeDo not reassign because of this setting. Ticket closure is handled separately by Auto-resolve call tickets.
OnNo task is identifiedDo not reassign because there is no identified incomplete parent task.
EitherThe call has no answering-agent recordNo direct reassignment is possible; normal ticket assignment continues.

The direct reassignment applies only to an open parent ticket. If the ticket is already resolved or no longer exists, Flowcall leaves it unchanged.

When AI follow-up for details missed on the call starts a follow-up, this reassignment waits until the follow-up ends. The ticket then goes to the answering agent if this setting is on, otherwise to the queue.

How processed call tickets are resolved​

Transcript processing and task inference still run when auto-resolve is off. The setting controls ticket closure, not whether the recording is transcribed or analyzed.

Auto-resolveTask completePending child ticketResult
OffEitherEitherKeep the call ticket open
OnNoNoKeep the call ticket open with its task and pending objectives
OnYesYesKeep the call ticket open until the child work is complete
OnYesNoResolve the ticket as Resolved by AI with the resolution Resolved on call

If transcription or task processing fails, the ticket remains open regardless of this setting.

Following up on details the call missed​

On a call, the customer often can't give everything the task needs, such as a serial number from the product label, the date they bought it, or a photo of the damaged product. With AI follow-up for details missed on the call on, the AI asks for these after the call and carries on with the ticket in the chat or email where the customer replies, as if the conversation had started there.

Example​
  1. A customer calls about a mixer that won't start. The transcript identifies the Warranty claim task, but the customer didn't have the serial number to hand and couldn't send a photo during the call.
  2. Right after the call, the customer gets a WhatsApp message (or the info request template when the 24-hour window is closed) and an email asking for the serial number and a photo.
  3. The customer replies on WhatsApp with the serial number and a photo. The AI continues the Warranty claim task in that chat with everything already collected on the call, saves the new values and the photo, and asks for anything still missing.
  4. From there the ticket behaves like a WhatsApp ticket: the task's actions run, and it resolves or goes to an agent according to the task.
When it runs​

A follow-up starts after transcript processing when all of these are true:

  • The setting is on and AI is enabled for voice calls.
  • Flowcall identified a task, and the task still has objectives that ask the customer (objectives with Ask user guidance), including photo, video and document objectives. Objectives meant for agents are never sent to the customer.
  • The call ticket wasn't resolved on the call, has no owner or assignee, and has no open child ticket.
  • The customer can be reached on WhatsApp or email.

If any of these isn't met, the ticket is assigned as described above.

Template and wait time​

The follow-up uses the Reply timeout from Customer Outreach under Ticket Lifecycle → Resolution & outreach, and the Info request template from WhatsApp Templates. The template is only used when the 24-hour WhatsApp window is closed, which is usual right after a call, and is sent without variables. Without a template, customers outside the window are reached by email only.

While the follow-up is open​

The call ticket stays in progress and shows a Waiting for customer (AI follow-up) card. An agent can Stop and send to agents from the card. The ticket's SLA starts when it reaches the queue, not while the AI is waiting for the customer.

When it ends​
  • The customer replies on WhatsApp: the AI continues the task in the WhatsApp chat. The ticket moves to the WhatsApp channel.
  • The customer replies to the follow-up email: the AI continues the task in that email thread. The ticket moves to the email channel.
  • No reply before the wait time ends, or an agent stops it: the ticket goes to the answering agent (when Assign incomplete call tickets to the answering agent is on) or the queue.
  • No message could be sent: the ticket goes to an agent straight away.