> For the complete documentation index, see [llms.txt](https://docs.voicemoat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voicemoat.com/getting-started/quickstart.md).

# Quickstart

**In short:** connect an account, train your voice, write your first post in Studio, reply with Engage or the extension, then schedule and measure. A few minutes end to end.

### 1. Connect an account

Sign in, then connect a **Twitter** or **LinkedIn** account. This is required: VoiceMoat needs a real account to learn your voice from and to post to. You can connect more than one later, on either platform.

See Connecting X and LinkedIn.

### 2. Train your voice

Open **Voice Lab** and build your voice profile. How it trains depends on the platform:

* **Twitter:** VoiceMoat reads your recent tweets through the Twitter API. Click to analyze. No upload, no paste.
* **LinkedIn:** use the Chrome extension to harvest your own recent posts in one click, or paste 5 to 10 of your posts if you would rather not install it.

Each platform gets its own voice, so train the one you want to work in first.

{% hint style="info" %}
Higher plans read more of your posts when training (up to 50 on Creator, 100 on Pro, 200 on Enterprise), so the voice profile has more to learn from. The first training is free; see Retraining your voice for later re-runs.
{% endhint %}

### 3. Write your first post

Open **Studio**, type a rough idea, and let audenAI draft it in your voice. Next to the draft you will see:

* a **voice-match score** ("N of M signals line up"),
* a **post coach** flagging craft issues,
* and an **engagement read** based on your own history.

Tighten it with a **tone** rewrite or the **Improve** pass, then post or schedule. On Twitter you can also build a **thread** (Pro and above). On LinkedIn you write a single post.

### 4. Reply in your voice

Go to **Replies**. The **Engage** tab surfaces posts worth replying to; pick a tone and audenAI drafts a reply in your voice.

* On **Twitter**, post through the reply window and mark it done.
* On **LinkedIn**, copy the draft and paste it as your comment.

Prefer to reply inside the feed? Install the **Chrome extension** and a reply coach appears on every post. See Chrome extension.

### 5. Schedule and measure

Set a posting schedule per profile in **Settings → Schedule**, then let **Analytics** show what is working, with a written read from audenAI on what to do more of.

### The daily habit

Most people settle into a simple loop:

1. check **Engage** for a few replies,
2. draft one post in **Studio**,
3. glance at **Analytics** once a week.

Everything stays in your voice, and most of the loop costs 1 credit per action.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.voicemoat.com/getting-started/quickstart.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.