---
title: Can You Route Calls by Location, Service, or Keywords?
description: "Routing by service, caller intent, location, or an approved urgency rule can be configured within your plan's scope. ## Examples - An estimate request reaches an approved sales contact. - An existing customer request follows a different intake path. -…"
url: "https://www.heyethan.ai/aireceptionist/docs/route-calls-by-location-service-or-keywords/"
updated: "2026-10-06"
category: Integrations + Workflows
---

# Can You Route Calls by Location, Service, or Keywords?

Routing by service, caller intent, location, or an approved urgency rule can be configured within your plan's scope.

## Examples

- An estimate request reaches an approved sales contact.
- An existing customer request follows a different intake path.
- A caller's service area helps determine the right approved route.
- An after-hours request follows the approved on-call or message path.

## Routing limits

Essential includes one primary path and transfer destination. Growth supports up to three approved paths or destinations. Professional supports up to five approved destinations. Additional locations and work beyond the included architecture receive a separate proposal.

## Rules need context

We review the wording callers use and how the assistant clarifies an uncertain request. Keywords are useful signals, but should not be presented as a guarantee that every call will be classified correctly.

## Review before launch

Every route needs a destination, an availability rule, and a fallback. We test these together.