Chatbot

Team workflows on the same desk as chat and help

Save a greeting for new conversation, live chat or email, inside or outside hours, a keyword in the first message, a visitor reply, resolve, reopen, or unassigned. Publish it. Matching events send that message, assign an owner, and add a tag. Routing still runs first. Team workflows on the same desk as chat and help.

  1. 1Starter chips on the widget
  2. 2URL teasers
  3. 3A live workflow greets
  4. 4A person replies
  5. 5Cove Agent draft

Triggers that persist

Publish a workflow under Workflows. It is saved. The next matching event can reply, assign, tag, wait, or branch. Routing still runs first. There is no calendar cron trigger — a Wait step resumes when /api/cron/workflows drains due runs (once a day) or when someone opens the desk.

TriggerIdWhat fires
New conversationfirst_messageVisitor starts a thread.
Visitor replymessage_receivedA later message on an open thread.
Inside / outside hoursbusiness_hours / after_hoursUses Settings → Hours. Not the visitor’s clock.
Channel is live chatwidget_openWidget only.
Channel is emailchannel_emailAfter Email is connected.
Keywordkeyword_matchFirst message contains your keyword. The reply is the text you wrote — the keyword is not echoed.
Resolved / reopenedconversation_resolved / conversation_reopenedState change on the thread.
UnassignedunassignedNo owner yet.

Steps: reply, assign, tag, wait (5 seconds to 1 day), branch on channel, hours, assignment, keyword, or tag. Cap 20 steps. Help: Live workflows.

FAQ

Frequently asked questions

Publish a workflow. It greets on the next matching event. Cron drains waits.

Yes. Open Workflows, write the message, and publish live. Use starter chips and URL teasers in Widget studio as well.

Starter messages, routing, workflows, and help articles a teammate can draft from.

Blog

Why teams switch the chatbox

Try it on a live inbox.

Fourteen-day trial. Card required. Cancel before day 14. Paste one script. Set the look.