What to set up next — a first-week checklist

Updated May 22, 2026

You've completed the basics — workspace created, widget configured, first message sent. The checklist below covers the six highest-impact things to set up next. None of them take more than 30 minutes and each one meaningfully improves the experience for your customers or your team.

1. Connect an email inbox

Customers who email your support address should land in the same inbox as your live chat conversations. Set up an email channel so you never miss a message regardless of where customers contact you.

To connect an email address, go to Settings → Emailing and follow the forwarding instructions. You can receive email with a forwarding rule from your existing support address (e.g. [email protected]) and reply directly from Yaplet.

Connect an email inbox →

2. Write your first five knowledge base articles

Every question your support team answers more than once is a candidate for a knowledge base article. Vex AI — your AI chatbot — uses these articles to answer visitors automatically. The more articles you have, the better it gets.

Start with the five questions your visitors ask most often. Common first articles: "How do I reset my password?", "What are your pricing plans?", "How do I cancel?", "Where's my order?", "How do I contact you?".

Create your first knowledge base article →

3. Turn on Vex AI

Vex is Yaplet's built-in AI agent. Once your knowledge base has a few articles, Vex can start answering common questions automatically — 24/7, in 100+ languages — and pass conversations to a human agent when you configure it to (by default Vex politely declines questions outside your knowledge base; auto-handoff is opt-in in Vex's settings).

To enable Vex, go to Automation → Vex, connect your knowledge base as a source, write a short persona prompt (who Vex is and what it should and shouldn't say), and toggle it on.

Set up Vex AI for the first time →

4. Enable bug reporting

Bug reporting lets your users report issues with a single click — attaching a screenshot, a session replay, console logs, and device metadata automatically. It takes the guesswork out of reproducing bugs and routes reports to a dedicated board where your team can triage and track them.

Yaplet creates a default bug-report form on signup. To surface it in the widget, open the widget editor, go to the Home tab, click Add card, and pick Form / Bug Report — the default bug-report form auto-fills in. Save. Submissions land on your Bugs board in the dashboard.

Enable bug reporting →

5. Try outreach or a product tour

Once your support is sorted, try reaching out to visitors proactively. Outreach lets you show a banner or a chat message triggered by visitor behaviour (time on page, specific URL, custom events). Product tours let you guide new users through your product with step-by-step tooltips anchored to your UI.

Both features live under Outreach in your dashboard's left sidebar.

Send a proactive message →   Build your first product tour →


You don't have to do all of this at once. Even completing items 1–3 in your first week will put you ahead of most new Yaplet workspaces. Come back to this list whenever you have a spare 30 minutes.

Did this article answer your question?