CHATBOTS

Split presales chat questions from support tickets automatically

Reads each incoming Zendesk chat, classifies it as a sales opportunity or a support request, answers product FAQs inline for support.

CategoryChatbots
Enginesim
Difficultyadvanced
Triggerevent
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew Zendesk chat messageZendeskZendesk
  • ActionClassify intent and draft support replyOpenAI
  • LogicSupport question or sales intent?
  • ActionPost answer back to Zendesk chatZendeskZendesk
  • ActionCreate HubSpot deal for sales intentHubSpotHubSpot
  • OutputAlert account executive in SlackSlack

What it does

Stops sales leads from drowning in your support queue. The workflow classifies every chat by purpose: support questions get an instant answer drafted from your knowledge base, while presales and buying questions are pulled out, turned into a HubSpot deal, and pushed to a sales rep — so revenue conversations never get treated like tickets.

When to use it

One chat widget feeds both support and sales, and good buyers keep getting answered like they have a bug. Use this when you want presales intent routed to revenue while support stays self-serve.

How it works

  1. 1A new Zendesk chat message triggers the workflow.
  2. 2OpenAI classifies the message as support or sales intent and drafts a reply when it's a known support topic.
  3. 3A logic branch splits the two paths.
  4. 4Support messages get the drafted answer posted back into the Zendesk conversation.
  5. 5Sales-intent chats create a HubSpot deal with captured context, then a Slack alert notifies the account executive on duty.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ZendeskTickets, queues, knowledge base.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect HubSpotCRM, deals, marketing, support.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.