Q: Is there a 1:1 onboarding session, and is it private?

A: Yes, 1:1 onboarding calls are available and are private to you. Group onboarding sessions are also offered for those who prefer them.

Q: Will I get help writing prompts?

A: Yes. The team offers direct support, and shares template prompts for common tasks like importing memory from another platform.

Q: If I miss a live session, will it be recorded?

A: Yes, sessions are recorded, and the recording and any related links are sent out afterward by email.

Q: I'm not very technical. What support is available to help me actually get value from this?

A: 1:1 onboarding calls, short 15-minute support call slots, and live onboarding teach-ins are all available, you don't need to figure it out alone.

Q: When is ChatChat more suitable than my existing technology stack?

A: ChatChat is most useful when work is recurring, context-heavy and spread across several tools, or when specialised agents need to support the same ongoing workflow. It can complement an existing stack rather than replace every application. A conventional tool or one-off chatbot may be more suitable for a simple single task, an already well-automated deterministic process or a regulated action that has not been designed with the required controls.

Q: What should I do if an agent appears stuck or shows a network error?

A: Wait briefly and retry once, check the internet connection, refresh or reopen ChatChat, and confirm that any required connector is still authenticated. If the task is large, try a smaller version. Do not repeatedly duplicate a heavy run. If the problem continues, capture the time, agent, task, screenshot and any available run receipt, then contact Support.

Q: What information should I provide when reporting a repeated technical problem?

A: Include the account email, agent and Living Brain name, exact prompt, time and timezone, device and browser, connector or skill involved, screenshot and complete error text, and any run ID, receipt or link. Also state whether the issue can be reproduced. This allows Support and Engineering to investigate the actual cause instead of guessing from a general error message.

Q: Why might a deep-research task repeatedly fail?

A: Possible causes include a runtime timeout, temporary provider failure, connector authentication issue, usage exhaustion, network interruption, unsupported source behaviour or a platform defect. The cause cannot be diagnosed safely without the prompt, timestamp, error message, agent, sources and any available receipt. Send those details to Support for investigation.