Onboarding questionnaire

Return answers to the questions below so Fonada can configure the platform to match your service. Anything left blank takes Fonada's default.

Traffic

  • 1. Which directions will you handle: inbound, outbound, or both?
  • 2. Expected peak concurrent calls, inbound and outbound separately:
  • 3. For outbound, expected ramp rate (calls per minute at campaign start):

Endpoint

  • 4. WebSocket URL, including any authentication parameter (wss:// preferred):
  • 5. Fixed URL for all calls, or per call?
  • 6. Which per-call values should Fonada put in the URL? ({session_id}, {customer_phone}, {business_phone}, {client_id}, {call_direction})
  • 7. Do you filter inbound traffic, and therefore require Fonada's egress addresses to allowlist?

Audio

  • 8. Sample rate for audio Fonada sends to you: 8000 or 16000 Hz?
  • 9. Sample rate you will send back: 8000 or 16000 Hz?
  • 10. Audio encoding: binary (default, recommended) or base64?
  • 11. Preferred chunk size: 320 or 640?

session_start payload

  • 12. Do Fonada's default field names work, or is renaming required? Provide the exact JSON field name required for each:
  • End user's number (default customer_phone)
  • Your platform number (default business_phone)
  • Call direction (not sent by default)
  • 13. What exact strings should Fonada send for inbound and outbound direction?
  • 14. Any metadata keys required, and for each, fixed or per call? (e.g. language, agent_id, campaign_id)
  • 15. Any fixed literal fields to include (account ID, API version)?

Behaviour

  • 16. Will you end calls via end_of_call?
  • 17. Do you require transfer to human agents? If so, which agent numbers, extensions, or queues should be reachable?

Contacts

  • 18. Technical contact for integration:
  • 19. On-call or escalation contact for production issues: