CUSTOMER SUPPORT
Intercom warm-touch when a customer's background jobs keep failing
Runs on a schedule, finds customers whose background jobs have repeatedly failed in the app database.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule: every few hours
- ActionAggregate failed jobs per customer in PostgresPostgres
- LogicClassify failure type, drop accounts with open tickets
- ActionLook up owner contact + planPostgres
- OutputOpen proactive Intercom conversationIntercom
- ActionPost batch summary to SlackSlack
What it does
Queries the application database on a cadence for accounts with a cluster of failed jobs (imports, syncs, exports) in a rolling window, then proactively opens an Intercom conversation with an offer to help — catching slow-burn problems that never spike loudly enough to trip a log alert.
When to use it
Best for failures that accumulate quietly: a customer whose nightly sync has silently failed three days running, or whose CSV imports keep erroring on a bad column. Use it when the pain builds gradually rather than all at once.
How it works
- 1A schedule trigger runs the check every few hours.
- 2Postgres aggregates failed jobs per customer over the rolling window and returns accounts above the failure count.
- 3A logic step classifies each by failure type to pick the right message variant and excludes accounts with an open ticket already.
- 4Postgres looks up the owner contact and plan tier.
- 5Intercom opens a proactive conversation with a type-specific message and a one-click reply to escalate.
- 6A Slack note posts the batch to the support channel so an agent can watch for replies.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect IntercomConversations, contacts, articles.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Customer Support workflows
Close the loop with requesters when a Linear bug moves to Done
When a Linear issue created from a support escalation moves to Done after deploy, look up the originating Zendesk tickets and notify each requester that their reported bug is…
Reopen and notify Front conversations when their bug fix deploys
When a deploy resolves a Sentry issue, find the snoozed or closed Front conversations linked to it, reopen them, and send the customer a reply that the fix is now live.
Suggest the right Loom video by classifying Intercom message intent
Reads each new inbound Intercom conversation, classifies what the customer is trying to do, and surfaces the best-matching Loom walkthrough to the agent as an internal note.
Draft personalized fix-live replies for support to review
When a Sentry issue resolves, an agent reads each linked ticket's full thread and drafts a tailored 'your fix is live' reply per requester.
Send a tailored Loom onboarding sequence on Front first-reply
When a new customer's first email lands in Front, this picks the Loom onboarding walkthroughs matching their plan and use case, builds a friendly sequenced reply.
Article Volume-Rebound Early Warning (Datadog)
Streams support ticket-tag events into Datadog, watches for topics whose volume is reaccelerating against a decaying article.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.

Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.
