kareenosdocs

Your first day checklist

The handful of things only a person can do after a build: approve automations, connect channels, add credentials, invite the team.

On this page

The build finishes with a short list of things only a person can do. Work through them in order and your project goes from built to running. Each item links to the page where you do it.

Note

While a project has no agent, sheet or page yet, the New Task page shows a getting-started checklist of its own under the task box: your account, your first agent, connecting WhatsApp or email, and inviting your team. This page is the fuller version for a finished build.

The checklist

  1. Approve every automation. Automations arrive switched off. Nothing runs, on any schedule, until a person approves it. Open Automations (level menu, Advanced, then Automations), open each one, read what it does and what it is allowed to touch, then approve. This is the single most common reason a new project looks finished but nothing happens.

  2. Connect your channels. Open Connections and press the + on each channel the project uses: WhatsApp, Telegram, Slack, phone calls, email. Send yourself one test message on every channel you connect. See Connections, Messaging channels and Voice channels.

  3. Add your credentials. Anything that reaches an outside system (a mailbox, a calendar, a payment account, your own database) needs your own login, entered on its card in Connections. The Super Agent never fills these in for you. Email is the one people forget, and a project that cannot email anybody looks finished until the first send fails, so start at Choosing an email option.

  4. Invite your team and place them in the right Team. In Teams, the last row of level 1, the Team someone belongs to decides what they can see and do, and which agents appear in their Inbox. Set this before people start working, not after.

  5. Check the Inbox flow. Open the Inbox and confirm the requests your agents raise read well. Then open it on a phone in the myKareenos app, because that is where most of your team will meet them.

  6. Walk the project. Open the project selector and choose Manage projects. On the Projects page: Overview, does the description read like your business? Components, is everything you expected there? Workflow, does the picture match how you would draw it on a whiteboard? Logs, is anything already reporting an error?

  7. Lock the project. Once you are happy, press the padlock in the project header on the Projects page. The design freezes so nothing can be rebuilt or edited by accident, while the project keeps running normally: agents answer, automations fire, rows are written. Unlock when you next want to change the design.

    The project header on the Projects page with its action buttons on the right: AI builder, publish to Marketplace, the padlock that locks the project, edit and delete

Important

Approving automations and locking the project are both deliberate human steps. No agent can approve an automation for you, and no agent can unlock a locked project.

If something looks wrong

Fix it by describing the problem in New Task rather than hunting for a setting. "Technicians are not getting their morning message" is a workable instruction. Check the project's Logs tab on the Projects page first so you can say what you saw.

Next