Every 15 minutes
Triage the support queue
Tags, sizes and routes each ticket before a person opens it.
ZendeskMCP
Escalation alert agentHear about the hot ones first.
Every 30 minutes it scans open tickets for signs of trouble: waiting too long, upset words, or a repeat contact. It posts a short alert with the reason, so a person can step in.
Your first signup includes $50 in free credits.
Every 30 minutes
Flag tickets before they blow up
- Reads
- Open tickets, threads
- Grows
- A short alert with a reason
- Lands in
- Slack
Ask for it once, in plain words.
No flowchart to draw. Describe the job in chat. TulipFarm sets up the agent and its workflow, and shows you both before anything runs.
You
Every 30 minutes, check open tickets. If one has waited more than a day, sounds upset, or has three replies with no fix, alert the support lead in Slack and say why.
TulipFarm
I made an agent called Escalation watch and a workflow that runs every 30 minutes. It reads open tickets through your Zendesk Custom MCP connection. Posting an alert to Slack asks you first. Activate it?
ActivateEdit first
One check for trouble.
Every run is saved as an agent task you can open, check and rerun.
- Schedule
Every 30 minutes
Run startedStarted - Reads
Open tickets and their replies
38 open tickets - Checks
Waiting over a day, upset tone, or 3 replies with no fix
3 flagged - Writes
One line on why each ticket was flagged
3 alerts - Asks first
Post the alerts to the lead in Slack
Approved - Posts
Message in Slack
DeliveredCompleted
What lands in Slack.
Only the tickets that need a person, each with the reason in plain words.
#support-leadsEscalation watch APP · 14:30
3 tickets need a look
Ticket #2102 · waiting 26 hours
- No reply since the customer's second message.
- Owner: Owner A
Ticket #2108 · upset tone
- The customer wrote that this is the third time they asked.
Ticket #2111 · 3 replies, not fixed
- Same error after each suggestion.
What gets planted.
Three parts you own and can change at any time.
- Agent
Escalation watch
Reads tickets and says why one needs help.
- Skill
Escalation rules
What counts as late, upset or stuck.
- Workflow
Every 30 minutes
Scans the queue on a timer.
Uses
- ZendeskMCPZendesk
- Slack
- Gmail
Add if you use it
- IntercomMCPIntercom
Google Sheets
HubSpot
It reads quietly. It asks before it acts.
Reads without asking
- Open tickets and their replies
- Your escalation rules
- A list of key accounts, if you add one
Asks you first
- Posting an alert to Slack
- Changing a ticket
- Sending any email
It uses your own connections, so it never sees more than you can.
Grow it your way.
Quiet hours
Hold alerts overnight and send one summary in the morning.
Key accounts first
Lower the bar for accounts on a list you keep in a table.
Page by severity
Send the worst to one channel and the rest to another.
Questions, answered.
Can it tell when a customer is upset?
It reads the words and gives its reason. It can be wrong, so each alert shows the reason and a person decides.
Will it reply to the customer?
No. It only alerts a person in Slack, and that post asks you first.
How does it see my tickets?
Through a Custom MCP connection to your help desk. It uses your own login, so it sees only what you can see.
Every hour
Handle refund requests
Checks the order and your policy, then drafts a reply for you to approve.
Mondays · 8:00
Collect what customers are saying
Pulls feedback from tickets and forms into themes and quotes.
No more surprises on Friday.
Public beta, open to everyone. Your first signup includes $50 in free credits.