Address not recognized or unusable
Describes the absence of a usable result or a confirmed address selection in the flow.
Limit : This symptom does not allow you to conclude that the address is outside coverage.
Help Centre · Field operations
Why is an address identified as outside the service area?
An address may be recognized or associated with a usable result without being covered by the applicable rules. An “outside service area” message does not automatically prove an input error, the complete exclusion of a postal code, or a lack of availability. This guide helps you reread the visible information before correcting the address, checking an authorized rule, or contacting support.
Distinguish address recognition from applicable coverage
Recognizing an address and reviewing its coverage answer two separate questions. A recognized address or one associated with usable information is not necessarily covered. Conversely, an “outside service area” message does not automatically mean the input is incorrect. A lack of availability is also a different symptom that must be reviewed in the booking flow. Before making any change, reread the visible address, the selected result when one exists, the available coverage information, and the exact displayed message. Do not change a rule solely to force acceptance of an address. A correction may improve input quality without guaranteeing that the address will become covered or that availability will be offered.
First check
Clarify the observed result
First identify the symptom that is actually visible. These situations do not lead to the same diagnostic.
Address reported as outside coverage
Describes a coverage-related message or result displayed in the context of the address being reviewed.
Limit : This result proves neither that the address is incorrect, that the entire postal code is excluded, nor that a rule must be changed.
Address accepted, but no availability
Describes a flow in which the address step appears completed but no booking period is offered.
Limit : A lack of availability does not prove a coverage refusal and must be reviewed separately.
Address
Reread the available address
Check only the information actually displayed in the flow being reviewed.
- The entered address or selected address.
- The street number and street when visible.
- The municipality or locality.
- The postal code when available.
- The recognized, suggested, or selected result when one exists.
- Differences between the entered text and the selected result.
Limit : The presence of a suggestion, position, detailed structure, or recognized result may vary. This article does not guarantee any address-resolution provider or perfect recognition.
Coverage
Review the coverage information
Reread the applicable information without inferring coverage from a single element.
Information to review
- The visible rule, area, or category when one exists.
- The exact displayed message or result.
- The booking or service context when relevant and available.
- Missing or contradictory information.
- The coverage intended by the organization under the applicable internal rules.
Keep in mind that
- A postal code alone is not enough to conclude that an address is covered.
- A recognized address or usable location information does not automatically prove coverage.
- The presence and level of detail of rules may vary.
- The displayed message does not necessarily reveal the exact business or technical cause.
Cautious decision
Avoid a premature change
A coverage change may affect other requests. Reread its scope before any authorized action.
- Reread the address before changing a rule.
- Do not expand coverage solely to force acceptance.
- Confirm that the person making the change is authorized under internal rules and the available functions.
- Review the visible or documented scope of the rule before changing it.
- Use only actions available and authorized in the flow.
- Record the result before and after the change when a documentation mechanism is available.
- Immediately reread the displayed message or result after the change.
Limit : Function names, permissions, available fields, history, and manual override options may vary by flow.
Conceptual flow
From reviewed address to the next step
Each step helps clarify the result without assuming a universal cause or correction.
Symptom clarified
The user distinguishes an unrecognized address, an outside-coverage result, and a lack of availability.
Limit : This distinction does not automatically reveal the exact cause.
Visible address reread
The input, selected result, and available address elements are reviewed.
Limit : The form and level of detail of the result may vary.
Usable result or issue documented
The available result is confirmed or the observed issue is described precisely.
Limit : A usable result does not prove coverage.
Coverage information reviewed
Applicable rules, areas, or information are reread when visible or documented.
Limit : Their presence and precision may vary; coverage should not be inferred from an isolated postal code.
Exact message reread
The exact wording and where it appears are recorded.
Limit : The message does not always identify the exact business or technical cause.
Next step selected
Depending on the result, the user may correct the address, check an authorized rule, continue the appropriate diagnostic, or prepare a support request.
Limit : No correction guarantees coverage, availability, a particular fee, or route generation.
Reference points
Distinguish address, coverage, availability, fee, and route
These concepts are related, but none should be inferred automatically from another.
Address and recognition
Address information that is recognized, selected, or otherwise usable for the next step in the flow.
Limit : It does not prove coverage.
Coverage
A result based on the rules or information applicable to the flow.
Limit : It does not guarantee that availability will be offered.
Availability
A period or time offered in the booking flow when availability can be calculated and displayed.
Limit : Its absence does not prove a coverage refusal.
Travel fee
A separate business rule when a fee applies.
Limit : The fee should not be inferred from the displayed distance alone.
Route
A route calculated from the usable data available.
Limit : A route does not prove coverage and does not guarantee future conditions.
Procedure
Check before continuing
Preserve the exact symptom, message, and context before correcting an address or rule.
- Identify the exact page and step.
- Record the exact message or result.
- Reread the address actually displayed.
- Check the selected or recognized result when one exists.
- Review the visible coverage rule, area, or category when one exists.
- Compare the result with the intended coverage under the applicable internal rules.
- Avoid changing a rule solely to force acceptance before understanding the result.
- Reread the result after an authorized correction or prepare a support request.
Note : A real check may modify data or affect future requests, and no universal simulation mode is guaranteed.
Guardrails
What this article does not guarantee
The diagnostic helps structure the checks. It does not guarantee a cause, correction, or particular operational result.
- That an address will always be recognized or usable.
- That a recognized address will be covered.
- That an outside-service-area message has one single cause.
- That the same rules, areas, fields, messages, or buttons exist everywhere.
- That a postal code or position alone determines coverage.
- That a phone number or contact option is displayed in the message.
- That a lack of availability means outside the service area.
- That route time is visible before assignment.
- That a correction will make the address eligible.
- That a manual override is available.
- That one specific provider or technical mechanism is used in every flow.
- That expanding a territory is appropriate or that a result will reduce detours, protect margin, increase billable time, or generate revenue.
Related resources
Continue with the right diagnostic
Choose the guide that matches the symptom or step you need to review.
Territories and routes
Choose the appropriate guide to review an address, fee, route, or optimization.
View the collection →Appointment booking
Learn about the documented functions related to services, durations, and booking models.
View the page →Why is no availability offered?
Review possible reasons for a flow with no offered period.
Read the guide →How are travel fees calculated?
Reread the applicable business rule when a fee is displayed or expected.
Read the guide →Why was a route not generated?
Check the visible information before concluding that there is an outage.
Read the guide →What does it mean to “optimize” a route?
Distinguish a calculated proposal from the final operational decision.
Read the guide →What data may MapMyStaff process?
Learn about the categories of information that may be involved depending on the functions used.
Read the guide →How do you prepare an effective support request?
Gather useful steps and results before contacting support.
Read the guide →Help Centre
Browse the other available collections and guides.
Visit the Help Centre →Support
Contact supportDocument the observed result
Please provide only:
- the page and flow;
- the exact step and symptom;
- the partially masked address;
- the selected or recognized result when one exists;
- the exact message;
- the visible rule, area, or category when one exists;
- the relevant booking or service context;
- the action attempted;
- the observed result;
- the approximate date, time, and time zone;
- a sanitized screenshot if useful.
Security instruction : Never send a password, authentication code, key, token, technical secret, unnecessary full address, or unnecessary personal information.