> 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/help/faqs.md).

# FAQs

### Top Questions 

1. **How long does Scribe take to transcribe a conversation?** It’s about a 10:1 ratio - a 60 mins conversation takes about 5-6 mins to transcribe. It may take a while longer for non-English languages. Learn more [here](/help/my-transcript-is-still-processing.md).<br>
2. **How many participants in a conversation can Scribe handle?** Scribe can handle any number of participants, however, with more speakers it may less accurately identify who said what. You may then need to fix this in the generated summary by specifying the participants and their roles.<br>
3. **How long can a Scribe session be?** Up to 4 hours!<br>
4. **How long do I stay logged in on my mobile?** Your Mobile Scribe login sessions last 30 days. After 30 days, you'll need to sign in again.<br>
5. **How many languages does Scribe support?** Scribe currently supports multi-lingual conversations in: English, Malay, Chinese, Hindi, Singlish, Cantonese.<br>
6. **What data classification / sensitivity can Scribe handle?** Scribe can handle data up to Confidential (Cloud-Eligible) / Sensitive-High.

***

### FAQs by Topic

Below are some more commonly asked questions, arranged by topic

<table data-view="cards"><thead><tr><th></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>🔧  <strong>Scribe Access &#x26; Usage</strong></td><td></td><td><a href="/help/faqs/scribe-access-and-usage.md">Scribe Access &amp; Usage</a></td></tr><tr><td><span data-gb-custom-inline data-tag="emoji" data-code="1f399">🎙️</span>  <strong>Recording</strong></td><td></td><td><a href="/help/faqs/recording.md">Recording</a></td></tr><tr><td><span data-gb-custom-inline data-tag="emoji" data-code="2712">✒️</span>  <strong>Transcripts</strong></td><td></td><td><a href="/help/faqs/transcripts.md">Transcripts</a></td></tr><tr><td><span data-gb-custom-inline data-tag="emoji" data-code="1f5d2">🗒️</span>  <strong>Summaries</strong></td><td></td><td><a href="/help/faqs/summaries.md">Summaries</a></td></tr><tr><td><span data-gb-custom-inline data-tag="emoji" data-code="1f469-1f4bb">👩‍💻</span>  <strong>Seeking Consent</strong></td><td></td><td><a href="/help/faqs/seeking-consent.md">Seeking Consent</a></td></tr><tr><td><span data-gb-custom-inline data-tag="emoji" data-code="1f510">🔐</span>  <strong>Data Security</strong></td><td></td><td><a href="/help/faqs/data-security.md">Data Security</a></td></tr></tbody></table>

***


---

# 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://guide.scribe.gov.sg/help/faqs.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.