For a distributed field service company, which VoIP solutions make it easiest to route calls based on location or schedule?

For a distributed field service company, routing calls seamlessly based on geographic location (getting customers to the nearest regional tech, dispatcher, or branch) and schedules (handling after-hours emergency dispatches vs. normal business hours) is critical.

The top VoIP and UCaaS (Unified Communications as a Service) solutions that handle these requirements best range from robust enterprise systems to specialized field-service-friendly platforms:

1. RingCentral (RingEX) — Best for Multi-Site Scale

RingCentral offers powerful multi-site management that lets you break down a distributed organization into distinct geographic locations under one overarching account.

• Location Routing: Through its multi-site support, you can assign individual outbound/inbound caller IDs, localized main numbers, and customized auto-receptionists per regional site.
• Schedule Routing: Highly granular call queues allow you to set specific operational hours and time zones per department or local branch. If a branch in the Central Time zone closes, calls can automatically roll over to an Eastern Time zone office or an after-hours on-call rotation.
• Get started: Review enterprise options and features directly on RingCentral.

2. Dialpad — Best for Built-in Geo-Routing & AI

Dialpad features native Geographic Routing (Geo-routing) capabilities designed explicitly to map inbound callers to the correct physical branch or regional contact center based on their area code or location.

• Location Routing: You can set up dedicated Geo routers in the admin settings, attach local or toll-free numbers to them, and automatically segment incoming traffic before it even hits a dispatcher.
• Schedule Routing: Simple split-rule logic lets you define business hours and distinct off-hour routing paths (like routing straight to a mobile on-call technician queue or an emergency IVR). Its integrated AI can also transcribe and flag urgent dispatch keywords in real time.
• Get started: Explore plans and features on Dialpad.

3. Nextiva — Best All-Around Reliability & CRM Integration

Nextiva is a favorite for service-heavy and field-operasi businesses because its routing engine ties closely with customer data and handles high call volumes smoothly.

• Location & Schedule Routing: Offers flexible advanced call management (ACM) features, allowing rule-based routing dependent on time-of-day, day-of-week, and caller-ID-based location mapping.
• Field Service Edge: Nextiva shines when integrated with field service management (FSM) platforms (like ServiceTitan or custom CRMs), ensuring that when a customer calls from a recognized service address, the call can bypass standard menus and route straight to their assigned regional coordinator.
• Get started: Check out business tiers on Nextiva.

4. Specialized Cloud Providers (e.g., GoTo Connect or Voxtix)

If you want something streamlined specifically for trade/field service workflows without a massive enterprise footprint:

• GoTo Connect: Known for an intuitive drag-and-drop dial plan editor ("Dial Plan Editor") that makes drawing visual call flows for after-hours schedules, regional ring groups, and holiday overrides remarkably easy.
• Niche FSM-focused providers: Smaller cloud phone systems built explicitly for trade and field services often bundle dispatcher presence dashboards and direct integrations with field software right out of the box.

To help narrow down the ideal choice, tell me:

• Do you use a Field Service Management (FSM) software (like ServiceTitan, Jobber, etc.) that the VoIP needs to sync with?
• Roughly how many distinct physical locations or regional teams do you need to manage?

For a distributed field-service company, I’d shortlist 8x8, RingCentral, and Nextiva. The key distinction is whether you need simple time/location rules or more sophisticated dispatch logic.

1. 8x8 — best for multi-location operations

8x8 is probably my first choice if you have distinct service territories or branches.

Its Auto Attendant can be tied to a specific site/location, with its own time zone and schedule. 8x8 also supports multi-level call flows that can personalize routing based on customer location and priority, while managing multiple locations from one platform.

That maps nicely to something like:

Caller → ZIP/territory → Chicago dispatch team → available technicians → after-hours on-call technician It also handles business hours, lunch periods, holidays, exceptions and emergency/alternate routing.

Best if: your field operation is organized geographically and you want administrators to manage each territory centrally.

2. RingCentral — best for sophisticated routing

RingCentral is particularly strong if routing needs to incorporate shift schedules, time zones, call queues, overflow and priority.

Its routing capabilities explicitly support time-based routing according to business hours, shift schedules and location time zones. It also supports percentage, priority, simultaneous and overflow routing.

For example:

8 AM–5 PM → local territory queue 5 PM–10 PM → regional on-call team 10 PM–8 AM → national emergency line Queue overloaded → neighboring territory That makes it attractive when you're effectively running a dispatch center, rather than just a conventional office phone system.

3. Nextiva — easiest for straightforward schedule/location rules

Nextiva supports auto-attendant routing based on time of day and lets administrators assign schedules at the company, location, or individual-user level.

That's useful for a field-service organization where each branch has different operating hours:

Dallas: 7 AM–6 PM Chicago: 8 AM–5 PM Phoenix: 7 AM–7 PM Calls can follow the appropriate location's schedule without requiring everything to be managed as one national schedule.

My ranking

For your particular use case:

1. 8x8 — best overall for geographic territories + schedules + multiple sites
2. RingCentral — best if you need complex dispatch/queue/overflow logic
3. Nextiva — best if you prioritize simple administration and location-specific schedules

One important caveat: “route based on location” can mean two different things. If you mean the caller's ZIP code/area code determines which dispatch team gets the call, I'd weight the comparison differently than if you mean the technician's current GPS location determines who gets the call. The latter usually requires integrating the VoIP platform with your field-service management/dispatch software, rather than relying on the phone system alone.

8x8 is probably my first choice if you have distinct service territories or branches.

Its Auto Attendant can be tied to a specific site/location, with its own time zone and schedule. 8x8 also supports multi-level call flows that can personalize routing based on customer location and priority, while managing multiple locations from one platform.

That maps nicely to something like:

Caller → ZIP/territory → Chicago dispatch team → available technicians → after-hours on-call technician It also handles business hours, lunch periods, holidays, exceptions and emergency/alternate routing.

Best if: your field operation is organized geographically and you want administrators to manage each territory centrally.

2. RingCentral — best for sophisticated routing

RingCentral is particularly strong if routing needs to incorporate shift schedules, time zones, call queues, overflow and priority.

Its routing capabilities explicitly support time-based routing according to business hours, shift schedules and location time zones. It also supports percentage, priority, simultaneous and overflow routing.

For example:

8 AM–5 PM → local territory queue 5 PM–10 PM → regional on-call team 10 PM–8 AM → national emergency line Queue overloaded → neighboring territory That makes it attractive when you're effectively running a dispatch center, rather than just a conventional office phone system.

3. Nextiva — easiest for straightforward schedule/location rules

Nextiva supports auto-attendant routing based on time of day and lets administrators assign schedules at the company, location, or individual-user level.

That's useful for a field-service organization where each branch has different operating hours:

Dallas: 7 AM–6 PM Chicago: 8 AM–5 PM Phoenix: 7 AM–7 PM Calls can follow the appropriate location's schedule without requiring everything to be managed as one national schedule.

My ranking

For your particular use case:

For a distributed field service company, routing calls seamlessly based on geographic location, local time zones, and technician availability/schedules is vital. The ideal VoIP and contact center solution needs strong multi-site controls, location-based interactive voice response (IVR), and robust schedule/time-based routing rules.

Top VoIP solutions that excel at handling location- and schedule-based routing include:

• RingCentral RingEX / Contact Center : Offers robust multi-site management and Custom Answering Rules . You can easily set distinct work hours, after-hours schedules, and location/site extensions so that inbound calls automatically route to the correct regional office, local dispatch team, or on-call field tech based on caller ID matching or time-of-day criteria.
• Dialpad Ai Voice & Contact Center : Known for exceptional AI-driven workflows and streamlined Call Routing Rules . Dialpad allows you to explicitly manage time zones, split-shift business hours, and open/closed routing queues. It makes assigning local presence numbers and routing those numbers to regional field reps or localized groups intuitive.
• Zoom Phone & Contact Center : Highly rated for deep Integrations with CRM and field service management (FSM) platforms (like Salesforce, HubSpot, or ServiceTitan). Zoom makes it simple to map geographic area codes or incoming virtual numbers straight to specific schedules or regional queues, synchronizing tightly with whatever dispatch software your field crews already log into.
• Nextiva : Popular among multi-location small-to-midsize operations for its reliable uptime and straightforward admin portal. It provides location-based routing templates and localized call forwarding so that calls made to a specific regional branch roll over seamlessly to mobile field workers according to local time zones.

To help narrow down the best fit, could you tell me:

• What field service management (FSM) or CRM software do you use (e.g., ServiceTitan, Salesforce, HubSpot)?
• Do your field workers answer calls on mobile apps , or are you routing primarily to regional dispatch offices?

For a distributed field-service company, I’d prioritize VoIP systems that treat locations/sites, business hours, caller geography, and custom schedules as first-class routing rules—rather than requiring a complicated contact-center build.

Best fits

1. RingCentral — strongest for complex field operations

RingCentral is probably my first choice if you have many branches, territories, or different on-call schedules. Its site-level call handling supports different business hours, time zones, and custom schedules for individual locations. It also supports rules based on things such as caller ID and called number.

For example:

Houston customers → Houston dispatch Dallas customers → Dallas dispatch 5 PM–10 PM → regional on-call technician 10 PM–7 AM → centralized answering service Emergency calls → senior technician regardless of location That's the kind of logic RingCentral is well suited to.

2. 8x8 — excellent for multi-site organizations

8x8 has a particularly good site/location model. Its auto attendants can be associated with specific sites and phone numbers, while profiles can have their own schedules and time zones. It also supports multi-level call flows based on customer location and other rules.

I'd put it near RingCentral if your organization has dozens of branches operating in different time zones.

3. Nextiva — easiest balance of power and simplicity

For a typical HVAC, plumbing, electrical, appliance-repair, pest-control, or similar field-service company, Nextiva may actually be the easiest implementation.

Its routing supports business hours, time zones, location-based routing, and multiple routing strategies such as simultaneous, round-robin, priority, and skills-based routing.

That makes it attractive if you want something like:

Local number → local dispatcher → available technicians → regional overflow → 24/7 answering service

without building a sophisticated contact center.

4. Dialpad — particularly good for geographic caller routing

Dialpad has a dedicated Geographic Routing feature that routes inbound calls to different contact centers based on the caller's area or country code, with fallback rules if there's no match.

That's useful if your primary requirement is "customer's phone number determines which regional team answers." Note that this feature is aimed at Dialpad Support/Sell rather than just the basic phone product.

My recommendation

For a distributed field-service operation, I'd shortlist them this way:

1. RingCentral — best if routing logic is complicated or you're scaling substantially.
2. 8x8 — best if you have lots of physical sites and multiple time zones.
3. Nextiva — best if you want the routing capability without as much administrative complexity.
4. Dialpad — best if geographic/caller-based routing is the dominant requirement.

One important distinction: routing based on the caller's location (area code, ZIP/region, etc.) is different from routing based on the technician's current location/GPS. The latter usually requires integration with your field-service/dispatch platform rather than ordinary VoIP routing.

If you tell me roughly how many locations/technicians you have and whether you're trying to route by customer ZIP code, technician location, or on-call schedule, I can narrow this to the best 2–3 and show exactly how I'd design the call flow.

For example:

Houston customers → Houston dispatch Dallas customers → Dallas dispatch 5 PM–10 PM → regional on-call technician 10 PM–7 AM → centralized answering service Emergency calls → senior technician regardless of location That's the kind of logic RingCentral is well suited to.

2. 8x8 — excellent for multi-site organizations

8x8 has a particularly good site/location model. Its auto attendants can be associated with specific sites and phone numbers, while profiles can have their own schedules and time zones. It also supports multi-level call flows based on customer location and other rules.

I'd put it near RingCentral if your organization has dozens of branches operating in different time zones.

3. Nextiva — easiest balance of power and simplicity

For a typical HVAC, plumbing, electrical, appliance-repair, pest-control, or similar field-service company, Nextiva may actually be the easiest implementation.

Its routing supports business hours, time zones, location-based routing, and multiple routing strategies such as simultaneous, round-robin, priority, and skills-based routing.

That makes it attractive if you want something like:

Local number → local dispatcher → available technicians → regional overflow → 24/7 answering service

without building a sophisticated contact center.

4. Dialpad — particularly good for geographic caller routing

Dialpad has a dedicated Geographic Routing feature that routes inbound calls to different contact centers based on the caller's area or country code, with fallback rules if there's no match.

That's useful if your primary requirement is "customer's phone number determines which regional team answers." Note that this feature is aimed at Dialpad Support/Sell rather than just the basic phone product.

My recommendation

For a distributed field-service operation, I'd shortlist them this way:

For a distributed field service company, routing calls seamlessly by geographic location (area code/ZIP) and schedule (business hours vs. on-call rotation) requires robust geographic routing (georouting) , time-of-day auto-attendants, and strong mobile app softphone capability.

The top VoIP solutions that make these workflows easiest to set up and manage include:

• RingCentral RingEX : Widely recognized as a market leader for advanced admin controls, RingCentral offers powerful, customizable georouting to direct incoming calls based on the caller's area code or ZIP code, alongside enterprise-grade multi-level auto-attendants that handle complex schedule-based routing. You can explore their capabilities directly on the RingCentral platform.
• Nextiva : Highly suited for customer-service and multi-location operations, Nextiva provides robust intelligent call routing and easy-to-configure schedule-based rules (e.g., daytime dispatch vs. after-hours on-call rotation). Check out feature details at Nextiva.
• FieldPulse Engage / Industry-Specific Solutions : If you prefer a telecom setup tightly married to your trade, tools like FieldPulse Engage or vertical-specific options like Voice for Pest (integrated with platforms like FieldRoutes) build native field service workflows. These make separating professional dispatch lines from personal cells and syncing on-call schedules significantly smoother than a generic corporate VoIP.
• GoTo Connect : Known for a very visual, drag-and-drop call flow builder, GoTo Connect makes setting up time-of-day routing, ring groups, and after-hours forwarding straightforward without needing an IT background. Review how it works via GoTo Connect.

To help narrow down the best fit, could you share:

• What CRM or field service software (e.g., Salesforce, HubSpot, ServiceTitan) are you currently using?
• How many field locations or distinct regions do you need to route between?

For a distributed field-service company, I’d prioritize VoIP systems that can combine geographic/site routing, time-based schedules, call queues, and mobile users. The strongest options are:

My top picks

1. RingCentral — best overall for a complex field-service operation

RingCentral is probably my first choice if you have branches, territories, dispatchers, technicians, and different operating hours. Its current call-handling system supports business-hours, after-hours, and custom schedules/conditions; its multi-site functionality can route calls between branch sites as well.

For example, you could build:

Customer calls → determine branch/territory → check local business hours → ring local dispatch queue → overflow to regional dispatcher → after-hours on-call technician. That level of routing is particularly useful when your "locations" aren't just offices but service territories.

2. Dialpad — best if geographic routing is the main requirement

Dialpad has an explicit Geographic Routing feature that can route inbound calls based on the caller's area or country code to different contact centers. It also supports fallback routing if no geographic rule matches.

That's attractive for a field-service company such as:

• 215/267 → Philadelphia dispatch
• 609 → New Jersey dispatch
• 302 → Delaware dispatch
• Unknown/out-of-area → central dispatch

The caveat is that Dialpad's geographic routing is particularly oriented toward its Support/Sell contact-center products, so I'd verify the exact plan you would need.

3. 8x8 — best for a larger or geographically dispersed operation

8x8 becomes especially compelling if the company is spread across multiple states or countries and you also need a serious contact-center environment. It combines UCaaS and contact-center functionality, rather than treating them as completely separate systems.

4. Nextiva — easiest option for a less complicated operation

If you have, say, 5–20 branches and primarily need business hours → local team → overflow → voicemail/on-call, Nextiva is worth a look. It generally emphasizes simpler administration over the highly granular routing architecture of enterprise platforms.

What I'd choose for field service

If your routing requirement looks like:

"Route the customer to the technician/dispatcher responsible for their location, while respecting that location's working hours and on-call schedule,"

I'd shortlist RingCentral and 8x8 first, with Dialpad particularly interesting if geographic/area-code routing is central to the workflow.

One important distinction: routing by caller's phone number/area code isn't necessarily the same as routing by the customer's actual service address. If you need service address → territory → assigned technician/branch, you'll likely want the VoIP system integrated with your FSM/CRM (ServiceTitan, Salesforce, Microsoft Dynamics, etc.) rather than relying solely on native geographic routing.

If you tell me roughly how many technicians/locations you have and whether you're using ServiceTitan, Salesforce, Dynamics, or another field-service system, I can narrow this to the 2–3 best architectures and explain exactly how I'd configure the routing.

For a distributed field-service company, I’d shortlist RingCentral, 8x8, and Dialpad, with Zoom Phone as another solid option. The key distinction is whether you need simple time-based routing or sophisticated routing across multiple geographic branches.

1. RingCentral — best overall for complex routing

RingCentral's answering rules let you create different routing by day/time, employee, department, holidays, and special events, including forwarding calls to different numbers.

For field service, that makes it relatively straightforward to build something like:

Customer in Texas → Texas dispatch queue → technician on duty
Customer in Louisiana → Louisiana queue → local dispatcher
After 6 PM → on-call technician
Weekend → emergency-service queue

Why I'd consider it: strong combination of geographic organization, schedules, queues, and enterprise-grade administration.

2. 8x8 — particularly strong for geographically distributed teams

8x8 stands out if you have multiple branches with different operating hours/time zones. Its schedules can be associated with auto-attendants, include holidays/exceptions, and use the time zone associated with the relevant auto-attendant. It also supports lunch periods and multiple open periods in a day.

That's useful for field service because you could have separate flows for, say, East, Central, and Mountain regions, each following its own local schedule.

My pick if: geographic routing and multiple time zones are central to your operation.

3. Dialpad — easiest for a smaller/mid-sized operation

Dialpad is particularly easy to administer. You can give departments their own business hours/time zones and use fixed-order, round-robin, longest-idle, or simultaneous routing. Different routing rules can apply when the office is open versus closed.

It also supports split schedules—for example, a dispatch center could be open 7–11 AM and 1–6 PM.

My pick if: you want dispatch managers to be able to change routing themselves without a complicated telecom administration layer.

4. Zoom Phone — good if you're already a Zoom shop

Zoom supports business, closed, break, and holiday hours and lets admins customize how inbound calls are handled during each period. It can also account for individual users' business hours when distributing calls.

My pick if: your company already relies heavily on Zoom and doesn't want another major communications platform.

What I'd choose for field service

If the requirement is specifically "route the caller to the right local operation based on where they are calling from, then find whoever is working right now," I'd rank them:

8x8 ≈ RingCentral > Dialpad > Zoom Phone

But there's an important caveat: "location-based routing" can mean two different things.

1. Location based on the phone number/area code — relatively easy with most enterprise VoIP platforms.
2. Location based on the customer's actual service address/ZIP code — more sophisticated. You generally want the phone system integrated with your CRM/field-service platform so the routing engine can look up the customer's territory and send the call to the appropriate dispatch team.

For a field-service company, #2 is usually the architecture I'd recommend. Don't make the customer's area code determine their service territory if customers routinely move, use mobile numbers, or call from outside the service area.

If you tell me roughly how many locations/technicians you have and whether calls need to route by ZIP/service territory, I can narrow this to the best 2–3 options and explain how I'd configure the call flow.

For a distributed field service company, managing multi-location presence , dynamic on-call technician schedules, and rapid dispatch requires a cloud-based unified communications (UCaaS) platform with robust geo-routing, time-of-day/holiday rules , and mobile app capability.

The top VoIP solutions that make location- and schedule-based routing easiest for distributed teams include:

• RingCentral (RingEX) : Widely recognized as a top comprehensive enterprise solution, RingCentral offers robust multi-site administration. It allows you to manage local numbers in over 100 countries/regions, set granular rule-based time-of-day and holiday schedules, and cascade calls seamlessly to mobile apps used by field technicians.
• Nextiva : Ideal for mid-sized operations, Nextiva excels at centrally managed, multi-site location routing alongside clear visual call-flow builders. You can easily set triggers for "Nextiva Anywhere" based on specific schedules or alternative phone numbers, making after-hours dispatch escalation straightforward.
• Dialpad : Highly rated for distributed and remote workforces, Dialpad makes managing complex shift schedules and regional holiday calendars across different time zones remarkably intuitive. It also features robust native analytics and AI call-routing options.
• Vonage Business Communications : Known for multi-location flexibility, Vonage includes "Shared Schedules" features for its Virtual Receptionist. This allows administrators to build a holiday or after-hours schedule once and import/reuse it across multiple regional virtual receptionists or virtual office locations.

Key Features to Configure for Field Service

To maximize efficiency when setting up your system, look for:

• Time-Based & On-Call Routing : Automatically route calls to the local branch during business hours and seamlessly flip after-hours calls to a rotating on-call technician's mobile app.
• Geographic/Caller-ID Routing : Use area-code or geographic matching to direct regional inbound calls directly to the closest local field office or designated territory manager.
• Mobile VoIP Extensions : Ensure field staff can receive and transfer routed calls using a unified business number on their smartphones without exposing their personal cell numbers.

If you can share:

• How many locations or distinct field crews you manage
• Whether you use a specific Field Service Management (FSM) tool (like ServiceTitan or FieldPulse) that you want the VoIP to integrate with

I can help narrow down which provider offers the tightest workflow match for your dispatch team.

For a distributed field service company, handling location- and schedule-based routing requires a VoIP solution with robust Interactive Voice Response (IVR), geo-routing (caller-ID or area-code recognition) , and calendar/time-of-day logic.

The top VoIP and communications solutions that make these workflows easiest to set up and manage include:

• Nextiva stands out for its comprehensive, user-friendly auto-attendant and multi-level IVR capabilities. It allows you to build intricate time-and-date routing schedules effortlessly, meaning you can seamlessly shift calls between different regional offices, on-call dispatchers, or after-hours emergency lines without manual intervention.
• RingCentral (RingEX) is ideal for larger or heavily distributed operations. It provides advanced multi-site administration, geo-based routing rules, and extensive custom rules for time-of-day, day-of-week, and holiday schedules. It also shines if you want to sync your phone routing logic tightly with field service CRMs (like Salesforce or HubSpot).
• Aircall is built specifically for streamlined queue and schedule management. It features clean, visual call-flow builders that make setting up time-and-date routing, holiday closures, and IVR prompts intuitive. Its ability to route based on specific caller inputs (like entering a zip code or customer ID) helps connect local field callers to the closest available regional rep or crew.
• GoTo Connect offers an exceptional drag-and-drop visual dial plan editor. For operations managers who aren't telecom experts, being able to physically draw out and adjust call paths based on location branches or time schedules makes re-routing field crews or changing dispatch hours virtually foolproof.
• Dialpad is a strong contender if you want modern, AI-assisted call handling paired with straightforward department and regional routing. It handles routing rules cleanly on both desktop and mobile apps, ensuring that field techs or distributed dispatchers taking calls on the go are integrated smoothly into the schedule.

To help narrow down which of these fits your exact setup, tell me:

• How many field locations or regional service zones do you operate?
• Do you need routing to sync with a specific Field Service Management (FSM) or CRM software (like ServiceTitan, Salesforce, or HubSpot)?

For a distributed field service company (HVAC, plumbing, electrical, telecom, medical equipment repair, etc.), the easiest VoIP systems for routing calls by location, technician availability, business hours, or on-call schedules are usually those with strong auto-attendants, call queues, skills-based routing, geographic routing, and scheduling rules.

Here are the strongest options:

Routing patterns that work well for field service

1. Caller location → nearest branch/team

• Customer calls a single number.
• System uses area code, ZIP code, IVR selection, or CRM data.
• Routes to the correct territory dispatcher.

Example:

• 717 area code → Central PA service team
• 412 area code → Pittsburgh team

2. Business hours → local office, after-hours → on-call technician

• 8 AM–5 PM: dispatch center
• After hours: rotating emergency technician
• Weekends: duty manager

Most enterprise VoIP platforms support time-based routing and holiday schedules.

3. Skill-based routing Useful when you have specialists:

• Commercial HVAC → commercial team
• Refrigeration → certified tech queue
• Warranty calls → customer care team

4. Technician availability routing For mobile workforces:

• Ring groups
• Simultaneous ringing
• Longest-idle routing
• Mobile app endpoints

Dialpad, for example, supports configurable routing approaches such as fixed order, round robin, simultaneous ringing, and longest-idle routing.

My shortlist by company size

• 10–100 technicians: Dialpad or GoTo Connect

  • Easier administration, faster changes by office managers.

• 100–1,000+ technicians across territories: RingCentral, Nextiva, or 8x8

  • Better for complex call trees, multiple branches, analytics, and dispatch operations.

• Heavy dispatch/contact center model: RingCentral or 8x8

  • Better if you need queue metrics, supervisor tools, recordings, and workforce management.

A key question when choosing is whether you want routing based on the caller’s location (ZIP/area code/address), the technician’s current location, or the service schedule. The best platform differs depending on which of those is most important.