Your First Conversation with Sarudo
What the AI-driven first-run onboarding looks like — the 11 essentials Sarudo collects in one conversation, and how deferred credentials work.
What This Article Is About (vs. Onboarding Process)
This is the AI-driven first conversation you have with your Sarudo AI employee on Telegram after your dedicated infrastructure is stood up. It is distinct from the Onboarding Process article, which covers the human 30-day timeline of consultation, setup, training, and handoff. Think of it this way: the human onboarding is what the Sarudo team does with you between day 1 and day 30. The first conversation is what happens in the first ten minutes of your first Telegram session with your AI employee — it sets up the essentials your AI employee needs to behave as yours from the very first task.
If the human setup team has already captured some of these essentials from your onboarding questionnaire, your AI employee will acknowledge what is already known and only ask for what is missing. The conversation is not a form — it is a check-in.
The 11 Essentials
In the first conversation, your AI employee asks for 11 pieces of context that shape every future interaction. Company name and a short description of what the business does. Your website and industry. The target audience or buyer profile you sell to. Your timezone and working hours (for scheduling and reminders). The tone you want the AI employee to communicate in (default: professional). Your primary email for outbound communications. And your Telegram user ID, which is captured automatically from the chat itself. Most of these are one-sentence answers, and the whole set usually takes under five minutes.
The opening of the first conversation
What your AI employee says when you first message it.
Deferred Credentials
Your AI employee does not ask for every integration credential up front. Integration keys (Twilio, Stripe, Notion, Airtable, Apollo/Clearbit/Hunter, your email password) are asked for only at the moment a task actually needs them. If you never ask your AI employee to make a phone call, it never asks for Twilio credentials. If you never ask it to query Notion, it never asks for a Notion token. This keeps the first conversation short and relevant — you spend time providing what you actually use, not filling out an up-front form of options.
When a task needs a credential, the AI will tell you specifically what is needed, where to get it, and any gotchas (for example, "you need a Gmail app password, not your regular password — here is how to generate one"). You are never left guessing.
Resetting a Fresh Instance
If you need a clean slate — a fresh demo environment, a reset after testing, a do-over because early answers were wrong — the reset procedure wipes the knowledge base, the conversation history, and any auto-created workflows. Resetting is a heavier operation than it sounds and has to be initiated by your setup team (it is not a /reset command in Telegram), because it intentionally requires a human-in-the-loop moment to confirm you really want to lose the context. After a reset, the next Telegram message triggers the 11-essentials conversation again from scratch.