Your support work, in one place with the rest of the company.
TulipFarm is an AI workspace where customer support teams keep ticket records, help-article drafts, escalations and weekly themes. Agents help with recurring work, and other teams use the same records.
Public beta, open to everyone. Your first signup includes $50 in free credits.
No account needed. The tour runs in your browser and doesn't connect to your accounts.
Where support meets the other teams.
Support trades work with Engineering, Product, Customer success and Marketing. Each handoff stays in the same workspace, so the next team picks up the original record.
Coming in
MarketingtoSupport
Launch FAQs
Marketing writes the launch FAQ and keeps it in Files. When customers ask about a release, your support agent can cite it in a draft reply.
TulipFarm for marketing teamsBack to the map
Going out
SupporttoEngineering
Escalations
When a ticket needs a fix, mark it Escalate in the Tickets table. A workflow can have your support agent summarize the ticket, and Engineering gets the summary in Slack after you approve it.
TulipFarm for engineering teamsBack to the mapSupporttoProduct
Weekly themes
Each week your support agent drafts the top ticket themes from the Tickets table. Once you've reviewed them, save the summary in Files and share it with Product.
TulipFarm for product teamsBack to the mapSupporttoCustomer success
Account flags
When an account keeps opening tickets, flag it in a table you share with Customer success. Each row lists the tickets behind the flag, so they start from the full history.
TulipFarm for customer success teamsBack to the map
The support work that comes back every week.
Ticket records go in tables, article drafts in Files, and the recurring work to agents or workflows. Set a job up once in chat, and the next run and the next teammate start from there.
In these examples, Fern is your team's support agent.
Ticket triage
When: Every morning
Import your ticket export into a Tickets table, with customer, topic, priority and status. Each morning, Fern proposes a topic and priority for new rows, and you approve the exact changes before they're saved.
Support playbook
When: Every draft
Save your tone, escalation rules and product terms as a skill and add it to Fern. Fern follows them when it drafts summaries and articles. Someone on your team saves and turns on each skill.
Help-article drafts
When: After each fix
Ask chat to draft a help article from the resolved tickets and your notes. It can write a Word document in Files, or propose a Google Doc that you approve before it's uploaded.
Escalations to engineering
When: Each escalation
Set up an escalation workflow in chat. When a ticket is marked Escalate, Fern drafts the summary, the run waits for your review, then Slack gets only the message you approved.
Weekly themes for product
When: Fridays
Schedule Fern to run on Friday afternoons. It reads the week's rows in the Tickets table and drafts the top themes in a private task for you to review.
TulipFarm isn't a helpdesk. Your team still answers customers from the tool it uses today, and TulipFarm works from the ticket records you bring in.
One escalation, start to finish.
An example: Priya, a support lead, has a ticket about failed exports that needs a fix. Here's how the escalation moves and where she stays in charge.
What the workflow and run statuses mean
Saved
Priya saved the workflow from chat. Nothing runs yet.
Activated
She turned it on. A change to a ticket row can now start a run.
Run started
Priya marked 3187 Escalate, so a run began.
Completed
The run sent the approved summary to #eng-escalations and finished. The ticket row stays in the Tickets table, ready to update when the fix ships.
Set up a workflow: when a ticket is marked Escalate, have Fern summarize it for #eng-escalations from the ticket row and my notes. Check with me before anything goes to Slack.
- Trigger
Priya sets ticket 3187 to Escalate in the Tickets table.
3187 set to Escalate - Condition
Checks whether 3187 is marked as a bug. If it's a how-to question, the run stops here.
Passed: bug - Agent
Fern reads the ticket row and Priya's notes in Files.
Read ticket and notes - Agent
Fern drafts a summary with the steps to reproduce, the affected customers and the priority, using the Escalation skill.
Draft ready - Review
The run pauses until Priya reviews the draft and responds.
Priya responded - Slack
Posts the summary to #eng-escalations once Priya approves the exact message. Nothing is sent before that.
Approved, sent to #eng-escalations
Completed means the run finished its steps. Check the run history to see what each step did.
What stays when the queue clears.
When someone goes on leave or a new teammate joins, nobody has to rebuild the support history from memory.
- Records
- Tickets, escalations and account flags stay in their tables.
- Context
- Help-article drafts, launch FAQs and weekly themes stay in Files.
- Decisions
- Workflow runs and approvals stay in run history, so you can see what was approved and what was sent.
- Procedures
- Skills, saved agents and workflows are ready for the next shift, so a new teammate starts with the same steps.
Questions from support teams
What is TulipFarm for customer support teams?
TulipFarm is an AI workspace where a support team keeps ticket records, help-article drafts, escalations and weekly themes, with agents and workflows for the recurring parts. Engineering, product, customer success and marketing work in the same workspace, so escalations, themes and launch FAQs can stay in one place instead of being copied between apps. TulipFarm Cloud is in public beta and open to everyone.
Does TulipFarm replace my helpdesk?
No. TulipFarm isn't a helpdesk and doesn't post replies in one. Your team keeps answering tickets where it does today and imports ticket exports into a TulipFarm table for triage, escalations and weekly themes. A new HubSpot ticket can also start a workflow. You can start with one recurring job, such as the weekly themes summary.
Can TulipFarm reply to customers automatically?
No. An agent can draft a reply or a help article for a person to review, but TulipFarm can't post replies in your helpdesk. If you connect Gmail, any draft or send an agent proposes waits until you approve the exact content.
How do review and approval work for support work in TulipFarm?
An agent proposes changes to table records, such as a ticket's topic or priority, and the person who owns the task approves the exact change before it's saved. A workflow can pause until a person responds, and a workflow step that sends a Slack message waits for approval of that exact message. Slack messages sent from chat or an agent task aren't held for approval, so check an agent's tools before you activate it.
Who can see customer tickets in TulipFarm?
Only the people you share them with. Private chats and agent tasks are visible only to the person who owns them, and workspace admins can't see them either. Project members see their project's chats and files, and you can share tables and files with the people who need them.
Can TulipFarm turn resolved tickets into help articles?
Yes, as drafts. Ask chat to draft an article from resolved tickets and your notes, and it can save a Word document in Files or propose a Google Doc that's uploaded only after you approve it. If you've connected Confluence, chat can also propose the article as a new page that's created only after you approve it. For other help centers, your team publishes the final article itself.
How do I get started with TulipFarm for support, and what does it cost?
Sign up for TulipFarm Cloud. The public beta is open to everyone, and your first signup includes $50 in free credits. Public paid plans haven't been announced; see the pricing page to ask for more credits or apply for student, NGO or startup support. You can also take the browser tour, called Explore, without an account; it doesn't connect to your business accounts.
Start with one queue.
Sign up for TulipFarm Cloud and set up the job you repeat most, like ticket triage or the weekly themes summary. The public beta is open to everyone, and your first signup includes $50 in free credits.
Want to check your tools first? Contact us about what your team uses.