Quick Start Guides
Your 5-step guide to building and deploying your first Myndy AI agent.
Welcome to Myndy. This guide walks you through the core steps to train, test, and deploy an AI agent—plus how to share public transcripts and audio recordings.
1) Create or Select a Workspace
Your Workspace is the top-level container for Agents, Knowledge Bases, and Tools.
- Open the sidebar → Workspace switcher.
- Use the default workspace, or create a new one for each brand/project.
What is a Workspace?
Think of a Workspace as a company or project. Every agent, document, phone number, and widget belongs to the active Workspace.
2) Build Your Knowledge Base
Your agent’s “memory” comes from your Knowledge Base (KB). Add data before linking it to an agent.
- Go to Knowledge Base in the sidebar.
- Add documents: Upload files (
.pdf,.docx,.txt), Add URL (site/FAQ), or Paste text. - Each item becomes reusable across agents inside the same workspace.
Good KB hygiene
Use concise, recent, and authoritative sources. Split large PDFs into logical sections for better answers and faster retrieval.
3) Create Your AI Agent
- Go to Agents → New Agent.
- Name it (e.g., “Support Bot”), pick a template if you like.
- In the Agent tab:
- System Prompt: define role, tone, boundaries.
- Think Model: select the LLM (e.g., GPT-4o class / Gemini).
- Speak Model: select a voice (Deepgram Aura family).
- Languages: choose primary + additional languages if needed.
- In Knowledge Base (inside the Agent tab):
- Find items from step 2 and toggle them Active for this agent.
Don’t forget the toggle
An agent only uses KB items that are explicitly toggled Active for that agent.
4) Test Your Agent (Voice & Chat)
Open the Test AI Agent panel in the agent editor.
- Chat Test: type messages and verify accuracy.
- Voice Test: have a live call with the agent.
- If answers seem off, confirm the KB item is Active and the prompt is clear.
When answers are stale
If you updated the prompt or KB, click Save Changes in the header. Unsaved changes don’t apply to tests or widgets.
5) Deploy the Website Widget
- In your agent editor, open the Widget tab.
- Customize color, position, and avatar.
- Copy the Embed Code and paste it right before your site’s closing
</body>tag.
Your widget now supports chat and voice on your site.
Public Transcript & Audio Pages
Myndy can email a transcript JSON and a .wav audio recording for each session. You can expose them on two public routes (no login required):
- Transcript page:
/conversation-transcript?source=<URL to transcript.json> - Audio page:
/conversation-audio?source=<URL to record.wav>
Example
-
Transcript:
https://myndy.ai/conversation-transcript?source=https://storage.googleapis.com/myndy-audio-transcriptions/<session>/transcript.json -
Audio:
https://myndy.ai/conversation-audio?source=https://storage.googleapis.com/myndy-audio-transcriptions/<session>/record.wav
The transcript page renders a chat-style view with user/assistant bubbles and avatars, scrollable history, and a Print Transcript action. The audio page displays a polished player with play/pause/seek.
CORS for transcripts
If your transcript URL is hosted on GCS/S3, add a CORS rule to allow your site
origin (e.g., https://myndy.ai, your preview domain, and localhost for dev).
Alternatively, proxy via a Next.js API route that sets
Access-Control-Allow-Origin.
Phone Numbers & Live Calling (Optional)
- Go to Phone Numbers → Buy a Number or Import Existing (Twilio).
- Connect a purchased/imported number to an agent using Connect Agent.
- Calls will appear in Conversations with recordings and transcriptions.
Best Practices
- Prompts: Keep goals explicit; add refusal rules and brand tone.
- KB scope: Only include content you want quoted or used as source.
- Versioning: Duplicate an agent when testing major changes.
- Security: Use separate workspaces for clients/brands.
Troubleshooting (Quick)
- Widget shows old behavior → Click Save Changes, then hard-refresh your site.
- Agent ignores a PDF → Ensure the PDF item is Active in the agent’s KB list.
- Transcript not loading → CORS not configured or URL private; use a proxy route.
- Audio not playing → Check file type (
.wav), content-type headers, and public access.