Skip to content

Before You Begin

Start here

Before building anything, confirm that you have the right workspace access, routing permissions, phone number, and one focused callback scenario.

Preparation keeps the first setup short and prevents the assistant from becoming too broad too early.

This onboarding path is for the workspace admin who wants one clear outcome: a Nuvoca Callback Assistant answering a real phone number without getting lost in advanced configuration too early.

Goal of this onboarding journey

Get from workspace access to a successful callback-assistant test call. By the end of the path, you should have a voice agent, a number assigned in Routing, and a call you can place yourself to verify the full callback flow.

Time estimate

Plan for 15 to 25 minutes if your workspace already has access to telephony and at least one available number.

Who this is for

  • Workspace admins or operators launching the first voice workflow in a tenant
  • Teams that want a working callback workflow before they invest in tools or knowledge bases
  • Users working mainly in the UI, not through the API

What this guide assumes

  • You are setting up a phone workflow, not just a chat-only assistant
  • You want one narrow use case first instead of a broad multi-purpose assistant
  • You are willing to use sensible defaults before tuning voice, tools, or document retrieval

What you need ready before starting

  • Access to a Nuvoca workspace
  • Permission to create agents and manage routing
  • A clear callback scenario for the first agent
  • At least one available phone number in the workspace, or a way to request one from your platform team
  • A team or inbox that should receive the callback request once the flow is working
  1. Read Launch Your First Voice Agent and follow it straight through to the first callback test call.
  2. Use Telephony if you need more detail on number purchase, assignment, or final call checks.
  3. Read How Nuvoca Works after first launch if you want the operating model in plain language.
  4. Add Tools or a Knowledge Base only after the callback flow works end to end.

If you do not need telephony yet

If your immediate goal is chat only, you can still use the same quick start and stop after the agent is created and sanity-checked. The main onboarding path assumes telephony, because the callback-assistant flow is designed around a real phone number.

Common blockers before setup begins

  • You can create agents but cannot manage numbers in Routing
  • The workspace has no available phone number yet
  • The team has not agreed on the first callback scenario, so the prompt stays vague
  • You are trying to solve tools or knowledge base design before the first live call works

If you hit setup problems, go to Common Issues before changing multiple settings at once.