# Get the best results (/docs/getting-started/best-results)

Skavelo answers from what it has seen: your app, through a test account, and your help docs. The more of your product that test account shows, the more Skavelo can explain and walk users through. Most gaps in its answers trace back to something it never got to see.

## Prepare the test account [#prepare-the-test-account]

This matters more than anything else on this page. Skavelo signs in with the [test account](/docs/teaching-skavelo/test-accounts) and opens buttons, menus and tabs to see what they show, so it only learns what that account can reach.

- **Finish your app's own setup.** If your app disables a button until onboarding is complete, such as **Create campaign** before a sending domain is added, Skavelo can't open it and won't learn that task.
- **Add sample items in each state.** Create at least one of each main thing in your product, like a project, a contact or a campaign. Where a menu changes with status, have one of each: a **Pause** option only appears on something that's running, and **Activate** only on a draft.
- **Give it a full role.** Use an admin or owner role, so screens that need permission aren't hidden from it.
- **Keep it apart from real customers.** Use your own email addresses for sample contacts. An active sample item in a marketing or billing tool can send real messages.

Skavelo blocks every change while it explores, so none of this sample data is altered.

## Add your help docs [#add-your-help-docs]

Add your help center or developer docs as a [website](/docs/teaching-skavelo/websites-and-web-apps) alongside your app. Your app shows Skavelo where things are; your docs tell it what they do and what happens next, such as what becomes of contacts already in a sequence you pause.

Add each site once. Two addresses that serve the same docs give Skavelo the same pages twice, which crowds out other knowledge.

## Check what Skavelo couldn't reach [#check-what-skavelo-couldnt-reach]

After each run, the agent's **Learning** tab lists what Skavelo couldn't reach under **What Skavelo couldn't reach**, with what to change for each one:

- a **Create** or **New** button that stayed switched off, with the reason your app gives in its tooltip;
- a screen with no items, so there were no rows or menus to open;
- a menu that only offered one side of a pair, such as **Activate** with no **Pause**, because every sample item was in the same state;
- a screen where your app signed the test account out.

The **Activity** log on the same tab shows everything Skavelo opened on each screen.

After you add the missing items, open the site's menu and choose **Re-learn every page**. **Learn what changed** skips screens whose controls look the same, so it can miss a new menu option.

## Review the walkthroughs [#review-the-walkthroughs]

Skavelo drafts walkthroughs for the tasks it finds. Open the agent's **Product map** tab to read them:

- Delete any that don't match how your team would do the task.
- [Write your own](/docs/walkthroughs/editing-walkthroughs) for the handful of tasks people ask about most.
- Try a few in your app before you go live.

When no walkthrough fits a question, Skavelo builds one from the screens it has mapped, as long as it has seen the buttons involved.

## Read Conversations every week [#read-conversations-every-week]

The agent's [Conversations](/docs/conversations/conversation-log) tab shows what people asked and how Skavelo answered. Look for:

- answers rated with a thumbs down;
- questions Skavelo answered in text where you expected it to show the steps;
- replies saying it can't show something on screen yet.

Each of these points to a fix: a missing section in your docs, a sample item for the test account, or a walkthrough to write.

## Tell Skavelo who's signed in [#tell-skavelo-whos-signed-in]

[Identify signed-in users](/docs/installing/identify-users) with their plan and role. Skavelo then fits its answers to what that person can do, and your team sees who asked each question.

## Point users to key tasks [#point-users-to-key-tasks]

Add two or three [suggestions](/docs/customizing/suggestions) on the pages where people get stuck most often. New users see what they can ask, and you guide them toward the tasks that matter.

## Give users a way to reach your team [#give-users-a-way-to-reach-your-team]

Set up [handoff](/docs/conversations/handoff), so a **Talk to a person** button leads to your existing support chat or email when Skavelo can't help.

## Add skills for simple actions [#add-skills-for-simple-actions]

[Skills](/docs/skills/creating-a-skill) let Skavelo carry out an action after the user approves it. They work best when the user can give every value in their own words, such as an email address or an amount, or when the value comes from the page they're on, as in "pause this automation" on that automation's page. Test each skill before you switch it on.

## Re-learn after each release [#re-learn-after-each-release]

New screens and renamed buttons reach Skavelo on its next run. It re-learns every week on its own, and you can [trigger a run from your deploy pipeline](/docs/developers/api-keys-and-deploys) so it stays current with every release.