How does setup work for routing sales calls separately from support calls?

For Fintech SaaS

During setup you define the qualifying questions and routing logic Voksha uses to determine caller intent within the first exchange, and for fintech SaaS this typically means distinguishing a prospect asking about pricing, a demo, or your SOC 2 report from an existing customer reporting a failed webhook, a billing discrepancy, or an onboarding issue with KYC document verification. You provide Voksha with your team structure (which queue or number sales calls should route to, which goes to support, whether security-review calls need a specific compliance contact) and the intent signals that distinguish them, such as whether the caller mentions being an existing customer, references an account or API key issue, or asks about implementation versus purchasing. Once configured, Voksha asks a short set of clarifying questions on the call itself, not just a menu tree, so a caller who says their payment reconciliation is failing gets routed to support immediately rather than sitting through a sales-qualification script. This solves the specific problem fintech SaaS companies flag most: billing and technical issues from existing customers landing on the sales line and consuming an AE's time meant for new pipeline. Setup for this routing logic typically takes longer than the basic phone and calendar connection, more like 20-30 minutes rather than 5, because it requires you to actually define your team's structure and intent categories, but it is done once and can be adjusted anytime as your team grows or reorganizes.