Knowledge
A knowledge base is optional. Attach your onboarding steps and the agent builds plans from them. It cannot change any knowledge base.
Customer onboarding automation agent that builds an onboarding plan for a closed-won deal (a deal marked as won in your CRM), creates Jira tasks once the account manager approves the plan and drafts a welcome pack in Notion. You give it the deal by mentioning it in Slack, Microsoft Teams or Telegram, or in Conversation.
What sales learned and promised often does not reach whoever runs onboarding, so new customers repeat themselves. A customer can go quiet and nobody notices until late. Onboarding tends to live in spreadsheets and email. Each new onboarding starts as a copy of the last one. The customer onboarding agent works from your own onboarding steps and writes a plan for each new customer. The account manager approves it before any Jira task is created.
Write your usual onboarding steps and what a welcome pack holds in a knowledge base and attach it to the agent. It reads the knowledge base and cannot change it.
In the agent's instructions, write what counts as a stalled customer. The agent applies your rule when you ask for a progress check.
Connect HubSpot or Salesforce, Jira and Notion. Connect Slack, Microsoft Teams or Telegram to talk to the agent there. Connect Google Docs if you want the plan written there. Connect Google Drive too if your onboarding documents live there. Add an MCP server, such as Figma or Adobe Firefly for design work, if the work needs another tool.
Mention the agent in Slack, Microsoft Teams or Telegram with the deal, in a channel it is invited to or in a direct message. You can also give it the deal in Conversation. The agent reads the deal from the HubSpot or Salesforce account you connect.
The agent writes the plan for the new customer in a Notion page, a Google Docs document or the chat reply.
The account manager reads the plan and approves it.
After approval, the agent creates the onboarding tasks in your Jira.
The agent writes a welcome pack draft for the new customer and saves it in Notion for your team to review. It does not send the draft to the customer.
Ask the agent how onboarding is going. It reads the Jira tasks and answers from them.
A knowledge base is optional. Attach your onboarding steps and the agent builds plans from them. It cannot change any knowledge base.
It reads the deal from the HubSpot or Salesforce account you connect and writes nothing back to it. The account manager approves the plan before the agent creates any Jira task. It creates and reads tasks only in the Jira projects you scope to it. It writes the plan in a Notion page, a Google Docs document or the chat reply. It saves the welcome pack draft as a page in Notion. It reads onboarding files from Google Drive and saves files there. It changes an existing document in Notion, Google Docs or Google Drive only when you ask. It reaches other tools, such as Figma or Adobe Firefly for design work, through an MCP server you connect. In Slack, Microsoft Teams or Telegram it acts only when mentioned or messaged directly. It does not send the welcome pack to the customer.
Web access is off by default, so it does not search the web unless you switch it on.
Message text is kept for 30 days, encrypted, to measure answer quality. Keeping conversations longer is your choice.
You give it a closed-won deal by mentioning the agent in Slack, Microsoft Teams or Telegram, in a channel it is invited to or in a direct message, or in Conversation. You start it by hand. It reads the deal from the HubSpot or Salesforce account you connect and does not write anything back to the deal.
Part of it. For customer onboarding automation, the agent writes the onboarding plan from your steps, creates the Jira tasks after the account manager approves and drafts a welcome pack in Notion. Your team handles the customer.
Yes. The account manager approves the plan before the agent creates any Jira task. It saves the welcome pack as a draft in Notion and does not send it to the customer.
You write the rule in the agent's instructions. Ask the agent for a progress check and it reads the Jira tasks and applies your rule. It does not set its own.
Yes, once you connect Jira. After the account manager approves the plan, the agent creates the onboarding tasks in the projects you scope to it. It reads those tasks when you ask for a progress check.
No. It saves a draft in Notion for your team to review.
Yes. It starts from a closed-won deal, so it works the same whether your company says customers or clients.
Researches a new inbound lead, qualifies it and drafts a reply for sales to approve.
Answers customers from your product docs in Slack, Teams, WhatsApp, Zendesk, Gmail and more.
Answers staff questions for every team from company documents, with sources.
Create an onboarding agent from this template, write your onboarding steps, then connect your CRM and Jira.