Workspace and Agent Setup
Engine 64 has two levels:
- A
workspacecontains your members, shared contacts, and one or more agents. - An
agenthas its own instructions, knowledge sources, conversations, analytics, and widget.
Use separate agents when the audience, source material, or handoff workflow is meaningfully different. Use a separate workspace when the data belongs to a different legal entity or team that should not share access.
Create the first workspace and agent
The setup wizard asks for your organisation name, website, and agent identity. Engine 64 checks the site’s sitemap and recommends pages to train from; when there is no usable sitemap, it discovers pages from the site instead. Review the list before starting the crawl—navigation, policy, pricing, and help pages are usually more valuable than campaign archives or tag pages.
To add another agent later, open Agents in the workspace and choose New agent.
Starting defaults
New agents start with:
- model:
GPT-5.4 Mini; - a welcome message based on the agent name;
- smart lead capture;
- a visitor limit of 5 messages every 30 seconds; and
- the submitted website hostname in the domain allowlist when setup can derive it.
Review these values before launch. Existing agents may retain older defaults until you change them.
Access and roles
Workspace membership is the access boundary. Owners and admins can manage sensitive configuration such as members and widget keys. Give regular members the least access they need, and remove people who no longer work with the workspace.
Names that stay useful
Name the workspace after the company or business unit. Name each agent after its job or audience—for example, Customer support, Trade enquiries, or New customer guide. Clear names make analytics and notifications easier to distinguish later.