> For the complete documentation index, see [llms.txt](https://guide.scribe.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.scribe.gov.sg/introduction/quickstart.md).

# Quick Start!

This guide will walk you through the steps to get you started. Before using Scribe in actual sessions, we recommend trying it out with a test conversation.

{% stepper %}
{% step %}

### Record Sessions on [<mark style="background-color:$primary;">mobile.scribe.gov.sg</mark>](https://mobile.scribe.gov.sg/)

* Log into [**mobile.scribe.gov.sg**](https://mobile.scribe.gov.sg) with your organisation's email (e.g. <john@open.gov.sg>).
* Select `Start Scribing` to begin recording your session.
  * Check that the sound bar moves when you speak - if it's not moving, no audio is being recorded.
* To save your session, select `Pause` then `Save` .
* Name your session.&#x20;
  * Choose a name that will help you identify it later.&#x20;

Once your transcript is ready, you can view it on your computer at scribe.gov.sg.

{% hint style="success" %}
Already have a transcript from a past conversation? [Upload it to Scribe](/guides/capture-a-session/upload-transcript-to-scribe.md) instead.
{% endhint %}
{% endstep %}

{% step %}

### Generate summaries on [<mark style="background-color:$danger;">scribe.gov.sg</mark>](https://scribe.gov.sg/)

{% hint style="info" %}
Transcripts and summaries can only be viewed on scribe.gov.sg on your computer, not on your mobile device.
{% endhint %}

* Log into [**scribe.gov.sg**](https://scribe.gov.sg/) with your organisation's email (e.g. <john@open.gov.sg>).
* Click on the session of interest to view its details.
  * You'll see the Default Overview of your conversation in your session page.&#x20;
* To generate your own summary, click `Generate Summary` .

<figure><img src="https://2400606950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFaQZ82l2KjVefurxtBBp%2Fuploads%2FdS1iSJBdlNPXH1YbXypY%2Fimage.png?alt=media&amp;token=b8553961-2591-401a-b0bb-d289d6cfd197" alt="" width="563"><figcaption></figcaption></figure>

* Click `Generate Summary`, then `By Sections`.
* Edit the description and section headers as needed, then click `Generate`.
  * A summary should be generated in less than 15 seconds.
    {% endstep %}
    {% endstepper %}

{% hint style="danger" %}
**Scribe uses advanced audio/language processing techniques and will have inaccuracies in its outputs**\
Users are strongly advised to review the outputs generated by Scribe for accuracy before relying on them for critical tasks or decisions
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guide.scribe.gov.sg/introduction/quickstart.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.