Introduction

Agent Setup configures the Vini agent for a rooftop and works through the "Agent Setup" checklist tasks. First, load the option lists that fill the agent form: voices, avatars and languages. Then work through the tasks in order: Agent Customization (create or update the agent), Assign Number, Service Policies, Upload Call Transcripts / Recordings and, for the receptionist only, Chatbot Script.

This stage is done once per agent. Mark each task done with the agent's segmentName. The segmentName values are listed in the Checklist introduction.

EndpointMethod and pathWhat it does
Browse the voice libraryGET /conversation/tts/voices/libraryReturns one page of voices to choose from.
List avatarsGET /conversation/avatarsReturns the avatars you can pick for the agent.
List voice languagesGET /conversation/tts/languagesReturns every language the agent can speak.
Get an agentGET /conversation/agents/team/{teamId}/enterprise/{enterpriseId}/agent-mapping/{teamAgentMappingId}Returns one existing agent's saved settings and voice.
Create an agentPOST /console/v1/product-onboarding/vini/agent (no agentId)Creates the rooftop's agent for one agent type.
Update an agentPOST /console/v1/product-onboarding/vini/agent (with agentId)Changes an existing agent's settings.
List agentsGET /conversation/agents/team/{teamId}/onboarded-agentsReturns every active agent on a rooftop, with its phone number.
Assign a phone numberPOST /console/v1/telephony/phone-numbersBuys a phone number and attaches it to one agent.
Get the agent configGET /central-config/v1/vini-config/agent-configReturns the rooftop-wide agent settings, including sales and service policies.
Save service policiesPOST /central-config/v1/vini-config/agent-configCreates or partly updates the rooftop-wide agent settings.
Upload call transcripts or recordingsPOST /console/v1/product-onboarding/vini/call-transcripts-recordings/filesUploads the dealer's sample call files to storage.
List chatbot scriptsGET /central-config/v1/smartview-scriptsReturns saved website scripts, one page at a time.
Save a chatbot scriptPOST /central-config/v1/integrationCreates or updates the website script that loads the receptionist chatbot.

Order to call them

  1. Load the form options: List voice languages, then Browse the voice library and List avatars.
  2. Agent Customization: Create an agent. If the agent already exists, Get an agent and then Update an agent.
  3. Assign Number: List agents to find the agent and check for a number, then Assign a phone number if it has none.
  4. Service Policies: Get the agent config, then Save service policies.
  5. Upload Call Transcripts / Recordings: Upload call transcripts or recordings, then save the returned URLs with Save service readiness answers.
  6. Chatbot Script (receptionist only): List chatbot scripts, then Save a chatbot script if the rooftop's website has none.

Which save completes which task

Checklist taskMark done as (taskName)Save callMarked done by the console UI
Agent customizationAgent CustomizationCreate an agent or Update an agentYes, after every successful save.
Assign phone numberAssign NumberAssign a phone numberYes, after a successful purchase. Not called when the agent already has a number, because the UI then skips the purchase.
Service policiesService PoliciesSave service policiesNo call from the console UI. These pages are edited in a separate settings app; whether that app marks the task done is to be confirmed.
Call transcripts and recordingsUpload Call Transcripts / RecordingsUpload call transcripts or recordings, then Save readiness answersYes, after both calls.
Chatbot script (receptionist only)NoneSave a chatbot scriptNo. The task counts as done once a script exists: the UI shows it done when List chatbot scripts returns a script with a scriptUrl. Nothing is written to the checklist.

The console UI marks tasks done with Mark a task done. segmentName is the tab's segment: inboundSales, outboundSales, inboundService, outboundService, acquisitionAiInbound, acquisitionAiOutbound, or receptionWebChat for the receptionist.

Authentication

Most calls need the Bearer token of a signed-in user, sent as Authorization: Bearer YOUR_TOKEN. The token is checked with the identity service. Every path starts with https://api.spyne.ai.

Service policies

Everything except policies is common to every agent. Service agents (inbound and outbound share these) save the entityConfig.service section with Save service policies and mark it done as Service Policies.


Did this page help you?