NORA · Pest Control

NORA Client Onboarding Guide

A complete, field-by-field guide to NORA's eight-step client onboarding questionnaire. Use it to prepare accurate answers so we can configure NORA around the way your pest control business actually operates.

Before You Start

NORA is the pest control Voice AI receptionist by Zeppelynn AI. This onboarding questionnaire collects the configuration inputs your team needs to prepare NORA for your business. Use the most accurate information you have. When an “Unsure” or “Needs review” option is available, choose it rather than guessing.

Gather the following before you begin:

Your authorized representative's name, job title, and direct contact details.
Your public business name (DBA) and the official registered legal name.
The legal structure your business is registered under (LLC, Corporation, etc.).
Whether you have a business tax identifier such as a US EIN — not the identifier itself.
Your primary business address, city, state/region, ZIP, and the time zone you operate in.
The services you actually offer, the ones you exclude, and any that require human review before booking.
The US states where you currently provide pest control services, and any applicable license references.
Whether your business performs structural fumigation or specialized wildlife trapping — both may require review.
Your real service area, approved prices for each service type, recurring plans, and warranty or guarantee terms.
Your approved safety guidance for treatments, including child/pet precautions and re-entry timing.
Your post-service review-request preference and, if applicable, your Google Business Profile review link.
Your scheduling software, booking mode, appointment types, operating hours, technician count, and capacity rules.
Your minimum booking notice, appointment buffer, and payment or deposit policy (never card numbers or credentials).
Your spoken greeting, dispatcher/office display name, escalation phone and email, and any backup contact.
Your language preference and the situations that should trigger a human escalation.
Your current SMS registration status, intended message categories, consent methods, and policy URLs.
Examples of your real SMS templates and any relevant privacy, terms, or disclosure wording.
Your existing telephone number, current carrier, and whether you'd prefer a new number, forwarding, or porting.
Your preferred area code, call-forwarding readiness, and SMS sending-line strategy.
The name and authority of the person who will sign off on the final configuration.

This form does not request your actual tax identifier, Social Security number, passwords, PINs, or account credentials. Do not enter them in free-text fields. The NORA schema has no file-upload fields — do not attempt to upload licenses, phone bills, or other documents here.

Contact & Legal Identity

Tells us who is authorized to represent the business and how to reach them, plus the public and registered identity of the company.

First Name

Required

What it means: The first name of the person authorized to complete this onboarding on behalf of the business.
What to enter: Enter the first name of your authorized representative exactly as they are known in your business.
Why we need it: This identifies the person responsible for the configuration decisions in this questionnaire and for any follow-up we need before activation.
Where to find it: Your authorized representative's name.
Example: Jordan
Common mistakes: Entering the name of a sales rep or contractor who is not authorized to approve the configuration.
If you are unsure: Use the name of the business owner or the person who can sign off on activation.

Last Name

Required

What it means: The last name of the authorized representative completing the onboarding.
What to enter: Enter the last name of your authorized representative.
Why we need it: Together with the first name, this identifies the responsible party for your record.
Where to find it: Your authorized representative's name.
Example: Rivera
Common mistakes: Leaving blank or using a nickname that does not match business records.
If you are unsure: Use the legal last name as it appears on your business records.

Job Title / Role

Required

What it means: The representative's job title or role at your pest control business.
What to enter: Enter the job title that reflects this person's authority (e.g., Owner, Operations Manager).
Why we need it: The title confirms the person has the authority to make the configuration decisions in this form.
Where to find it: Your business's staff records or your representative's business card.
Example: Owner
Common mistakes: Entering a generic role that does not reflect actual authority, such as 'Helper' or 'Receptionist' when the person is the owner.
If you are unsure: Use the title that most accurately reflects who is approving NORA's configuration.

Primary Contact Email

Required

What it means: The email address where our team should send follow-up questions and review notifications.
What to enter: Enter a working email address that your authorized representative actively monitors.
Why we need it: This is the primary channel for our review team to contact you about your onboarding answers before activation.
Where to find it: Your representative's business email account.
Example: jordan@yourbusiness.com
Common mistakes: Using a no-reply or shared inbox that nobody checks, or a personal email you rarely read.
If you are unsure: Use the inbox your owner or operations lead checks daily.

Direct Mobile Phone

Required

What it means: A direct mobile phone for the authorized representative, in US or international format.
What to enter: Enter the number with country code and standard spacing, hyphens, or parentheses — the field accepts both.
Why we need it: A direct line helps us reach the right person quickly for time-sensitive onboarding questions.
Where to find it: Your representative's mobile phone.
Example: +1 650 241 9598
Common mistakes: Entering the main office line instead of the representative's direct mobile, or dropping the country code for an international number.
If you are unsure: Enter any direct number where our team can reach the authorized person. Do not enter a shared front-desk number.

Public Business Name (DBA)

Required

What it means: The name your customers see — the name you trade as publicly, also called a 'doing business as' name.
What to enter: Enter the public-facing name customers recognize.
Why we need it: NORA introduces your business to callers by name, so this should match your signage, website, and ads.
Where to find it: Your website header, signage, social profiles, and marketing materials.
Example: GreenShield Pest Control
Common mistakes: Entering the legal entity name when customers only know the DBA, or vice versa.
If you are unsure: Use the name a customer would recognize when they call your office.

Official Legal Business Name

Required

What it means: The full registered legal name of the business entity, as it appears on state filings.
What to enter: Enter the exact registered name, including any designation like 'LLC' or 'Inc.' as filed.
Why we need it: The legal name is used for compliance and identity matching during onboarding review, separate from the DBA.
Where to find it: Your state business registration, articles of organization/incorporation, or tax filings.
Example: GreenShield Pest Control LLC
Common mistakes: Confusing the DBA with the legal name, or dropping the entity designation (LLC, Inc.).
If you are unsure: If your business structure makes the legal name unclear, indicate that you need clarification rather than guessing.

Legal Business Structure

Required

What it means: The legal form of your business entity.
What to enter: Select the structure your business is registered as: Sole Proprietor, LLC, Corporation, Partnership, Nonprofit, or Other.
Why we need it: The structure affects how we match your identity and what compliance documentation may be relevant.
Where to find it: Your state registration or formation documents (articles of organization/incorporation).
Example: LLC
Common mistakes: Selecting 'Sole Proprietor' when the business is actually an LLC, or guessing the structure.
If you are unsure: Select 'Unsure — please help me determine the correct category' so we can help you confirm it.

Business Tax ID Availability

Required

What it means: Whether your business has a US EIN or other applicable business tax identifier. This asks only whether one exists — never the identifier itself.
What to enter: Select whether you have a business tax identifier, do not have one, or are unsure which registration path applies.
Why we need it: We need to know whether a business tax identifier exists for registration planning, but the identifier itself is sensitive and should never be entered here.
Where to find it: Your CPA, bookkeeper, or your business tax records — only to confirm it exists, not to copy it.
Example: I have a US EIN or other applicable business tax identifier.
Common mistakes: Pasting the actual EIN or SSN into a free-text field. Never enter the identifier itself in this form.
If you are unsure: Select 'I am unsure which registration path applies' and our team will help you confirm it. Never paste the identifier.

Primary Business Address

Required

What it means: The primary street address of your business.
What to enter: Enter the full street address, including suite or unit number if applicable.
Why we need it: The address is used for service-area context and identity verification, not for inferring coverage.
Where to find it: Your business lease, registration, or website contact page.
Example: 1200 Industrial Blvd, Suite 210
Common mistakes: Using a home address when the business is registered elsewhere, or omitting a suite number.
If you are unsure: Use the address that matches your state business registration.

City

Required

What it means: The city of your primary business address.
What to enter: Enter the city name as it appears on your business records.
Why we need it: Completes your primary business location for accurate identity and routing context.
Where to find it: Your business address records.
Example: Phoenix
Common mistakes: Using a neighborhood name instead of the official city.
If you are unsure: Use the city listed on your state registration.

State / Region

Required

What it means: The US state or region of your primary business address.
What to enter: Select your state from the dropdown, or the clarification option if outside the US.
Why we need it: State affects applicable licensing and regulatory context for your business.
Where to find it: Your state business registration.
Example: AZ
Common mistakes: Selecting a state where you have clients but are not registered, or skipping the clarification option when outside the US.
If you are unsure: If outside the listed US jurisdictions, select 'Outside the US — please clarify my jurisdiction' so we can review.

ZIP / Postal Code

Required

What it means: The ZIP or postal code for your primary business address.
What to enter: Enter a five-digit US ZIP or a ZIP+4. Leading zeros are preserved — do not enter as a number.
Why we need it: Completes the address for identity verification and accurate geographic context.
Where to find it: Your business address records.
Example: 85007
Common mistakes: Dropping leading zeros (e.g., '02110' becoming '2110') by typing it as a number instead of text.
If you are unsure: Use the ZIP that matches your state business registration address.

Primary Business Time Zone

Required

What it means: The time zone your business operates in for scheduling and call handling.
What to enter: Select your time zone (Eastern, Central, Mountain, Arizona, Pacific, Alaska, or Hawaii).
Why we need it: NORA uses the time zone to interpret operating hours and after-hours logic correctly. It is not inferred from your browser or IP.
Where to find it: Your office's actual operating time zone — not your current browser location.
Example: America/Phoenix
Common mistakes: Selecting the time zone of a remote team member instead of the business, or relying on a browser auto-detect.
If you are unsure: Select 'Other / Unsure' and tell us where your office actually operates so we can confirm.

Operational Scope & Licensing

Defines the services NORA may discuss, the ones it should avoid, and the licensing and geographic scope of your business.

Services Offered

Required

What it means: Which pest control services your business actually provides. These are the services NORA may discuss and book.
What to enter: Select every service you genuinely offer. At least one is required. Select 'Other' if you offer something not listed.
Why we need it: These selections shape NORA's service information and call-handling rules. Selecting a service you do not actually offer leads to misdirected bookings.
Where to find it: Your service menu, website, and the work your technicians actually perform.
Example: General Pest Control, Termite and WDO Inspections, Rodent Control and Exclusion
Common mistakes: Selecting every category to appear full-service, or selecting a service you subcontract without clear approval.
If you are unsure: Select only the services your team directly performs today.

Other Services Description

Conditional

Appears only when 'Other' is selected under Services Offered. It becomes required while 'Other' is selected.

What it means: A description of the additional services you offer that were not in the standard list.
What to enter: Describe each other service you offer in plain language.
Why we need it: So we can map your additional services into NORA's service information and call-handling rules accurately.
Where to find it: Your service menu or the work your technicians perform.
Example: Snake removal and exclusion from crawlspaces
Common mistakes: Leaving blank while 'Other' is selected, which blocks progression.
If you are unsure: If you are not sure whether a service qualifies, leave 'Other' unselected and use only the listed categories.

Services Not Offered

Optional

What it means: Services NORA should identify as unavailable so it does not promise work you do not perform.
What to enter: Select any standard categories you do not offer. There is a separate 'No additional exclusions' option that clears the rest when chosen.
Why we need it: This prevents NORA from booking or quoting services your business does not provide.
Where to find it: Compare the standard list against the services your team actually performs.
Example: Bed Bug Heat or Chemical Treatments
Common mistakes: Selecting a service as both offered and not offered — the form blocks that conflict. Also, selecting 'No additional exclusions' and other exclusions at the same time is not allowed.
If you are unsure: If you offer every listed service, choose 'No additional exclusions.' If unsure, leave the field optional.

Services Requiring Human Review

Optional

What it means: Services that, even though you offer them, should be referred to your team rather than booked directly — for example, work needing a specialist assessment or custom quote.
What to enter: Select any offered services that require a human assessment before booking.
Why we need it: These are review requirements, not exclusions. A service can be offered and still require human review.
Where to find it: Your internal booking policy and any services that need a site visit or custom quote.
Example: Commercial Pest Management
Common mistakes: Confusing this field with the not-offered field. A service can be offered and still require human review.
If you are unsure: Leave it blank if you are unsure. You can add review requirements later without changing what you offer.

Pesticide or Pest Control License Number

Optional

What it means: A reference to your applicable pest control license, if available.
What to enter: Enter the license reference if you have one. It may contain letters, numbers, and hyphens.
Why we need it: Our team reviews any licensing relevant to your business and service area. Entering a number does not prove legal compliance.
Where to find it: Your state pesticide regulatory license card or records.
Example: AZ-PCO-102345
Common mistakes: Assuming entering a license number proves compliance — it does not. We review applicable requirements separately.
If you are unsure: Leave it blank. Our team will review applicable licensing requirements with you before activation.

Operating States

Required

What it means: The US states where your company currently provides pest control services.
What to enter: List the states you actually serve. State names or abbreviations are both accepted.
Why we need it: State coverage affects licensing and service-area configuration. Listing states does not configure multi-branch routing.
Where to find it: Your service-area records, dispatch territory, and active client addresses.
Example: California, Nevada
Common mistakes: Listing states where you only have a single past client but no active service, or leaving the field blank.
If you are unsure: List only the states where you currently perform work. Add or remove later if needed.

Structural Fumigation Scope

Required

What it means: Whether your business performs structural fumigation, including tent fumigation — a scope-sensitive service that may require additional review.
What to enter: Select Yes, No, or Unsure. This is a required scope question.
Why we need it: Structural fumigation may require custom safety and routing rules. Answering Yes or Unsure routes you to a manual scope-review screen that preserves all your answers while we review.
Where to find it: Your service menu and the work your team is licensed and equipped to perform.
Example: No
Common mistakes: Selecting Yes to appear full-service when you do not actually perform fumigation.
If you are unsure: Select 'Unsure' — it routes you to the same manual review path so we can help confirm scope.

Specialized Wildlife Scope

Required

What it means: Whether your business provides specialized wildlife trapping or removal that may require custom safety or routing rules.
What to enter: Select Yes, No, or Unsure. This is a required scope question.
Why we need it: Specialized wildlife work may need separate operational review. Answering Yes or Unsure routes you to the manual scope-review screen.
Where to find it: Your service menu and wildlife-handling capabilities.
Example: No
Common mistakes: Treating ordinary rodent control as specialized wildlife — this question is about specialized wildlife work, not routine rodent jobs.
If you are unsure: Select 'Unsure' — it routes you to the same review path so we can help define the correct scope.

Services, Pricing & Reviews

Captures your service area, approved pricing, safety guidance, warranties, and review-request preferences so NORA reflects what your business actually authorizes.

Service Area Description

Required

What it means: The cities, counties, or geographic boundaries where your business actually provides service.
What to enter: Describe your real service area in plain language. Preserve line breaks if helpful.
Why we need it: NORA must not promise service outside the areas your team approves. We do not infer coverage from your business address.
Where to find it: Your dispatch territory, service-area page, and active client locations.
Example: Maricopa County and north Pinal County, within 30 miles of our Phoenix office.
Common mistakes: Listing states instead of the actual local area, or over-broad regions.
If you are unsure: Describe the area your dispatch team actually serves today.

Service ZIP Codes

Optional

What it means: Known service ZIP codes or groups of ZIP codes, if available.
What to enter: Enter specific ZIPs, ranges, or grouped codes. Free-form notes are allowed since clients may use ranges or groupings.
Why we need it: Helps us understand your precise coverage. Multi-territory routing is configured separately.
Where to find it: Your dispatch or service-area records.
Example: 85001, 85004, 85008
Common mistakes: Applying a rigid numeric pattern that rejects valid ranges or grouped codes.
If you are unsure: Leave blank if you do not track ZIP-level coverage precisely.

Pricing Disclosure Mode

Required

What it means: What NORA is authorized to say about pricing — quote approved prices only, give starting prices, or never quote and route to a human.
What to enter: Choose a policy your business genuinely authorizes. No prices become active until the configuration is reviewed.
Why we need it: This determines whether the price fields below are required and how NORA may talk about cost.
Where to find it: Your owner or pricing manager's approved policy.
Example: NORA may quote only the exact prices and ranges approved below.
Common mistakes: Selecting approved prices without actually entering approved values, or choosing a mode the business does not authorize.
If you are unsure: Choose 'human quote' so NORA captures the request and routes it to your team.

General Pest Price

Conditional

Required when the pricing mode is 'approved prices' or 'starting prices.' Optional when the mode is 'human quote.'

What it means: Your approved general pest treatment or inspection price.
What to enter: Enter your actual approved price or range. Do not enter demo or placeholder pricing.
Why we need it: When you authorize NORA to quote, this is the value it uses for general pest work.
Where to find it: Your current price sheet approved by ownership.
Example: Free inspection, $89 inspection fee, or $150–$250 treatment
Common mistakes: Entering a made-up price or copying a competitor's price.
If you are unsure: Switch the pricing mode to 'human quote' so NORA routes pricing questions to your team instead.

Termite Inspection Price

Optional

What it means: An approved price or range for termite inspections, only if you offer them.
What to enter: Enter an approved price only if your company performs termite inspections.
Why we need it: Keeps NORA's termite pricing accurate when relevant.
Where to find it: Your approved price sheet for termite work.
Example: $150 termite inspection
Common mistakes: Entering a price for a service you do not actually offer.
If you are unsure: Leave blank if you do not perform termite inspections.

Termite Treatment Price

Optional

What it means: An approved starting price, range, or 'Assessment required' note for termite treatments.
What to enter: Enter an approved price, range, or 'Assessment required.' Do not invent a price.
Why we need it: Keeps NORA's termite treatment quotes accurate.
Where to find it: Your approved price sheet for termite treatments.
Example: Assessment required
Common mistakes: Inventing a price when treatment requires a site assessment first.
If you are unsure: Use 'Assessment required' rather than guessing a number.

Follow-Up Price

Optional

What it means: The approved price or range for chargeable follow-up or re-service visits.
What to enter: Enter an approved chargeable price or range, if applicable.
Why we need it: Keeps NORA's follow-up pricing accurate when a re-service is chargeable.
Where to find it: Your service agreement and approved price sheet.
Example: Included with plan, or $75 per follow-up
Common mistakes: Assuming all follow-ups are free when some are chargeable.
If you are unsure: Leave blank if you do not charge separately for follow-ups.

Recurring Service Plans

Required

What it means: Whether your business offers recurring pest management plans.
What to enter: Select Yes, No, or Unsure.
Why we need it: Determines whether NORA may discuss recurring plans and whether plan details are required.
Where to find it: Your service offerings and sales process.
Example: Yes
Common mistakes: Selecting Yes without then describing the plans you actually offer.
If you are unsure: Select 'Unsure' — we will help confirm recurring-plan information before NORA answers questions about it.

Recurring Plan Details

Conditional

Required when Recurring Service Plans is set to 'Yes.' Not required for 'No' or 'Unsure.'

What it means: A description of your approved recurring plans and pricing.
What to enter: Include plan names, billing frequency, included visits, initial fees, and any important limitations.
Why we need it: NORA needs accurate plan details to discuss recurring service correctly with callers.
Where to find it: Your recurring service agreements and price sheet.
Example: Quarterly plan: $120/quarter, 4 visits/year, $50 initial setup, re-service included.
Common mistakes: Entering plan names without pricing, or pricing without describing what is included.
If you are unsure: Set Recurring Service Plans to 'Unsure' and we will confirm plan information before activation.

Pricing Notes

Optional

What it means: Additional pricing policies or quote requirements not covered by the specific price fields.
What to enter: Describe inspection requirements, property-size considerations, commercial quote procedures, taxes, fees, or services needing an on-site assessment.
Why we need it: These are notes for the implementation team — not every note is automatically interpreted by NORA.
Where to find it: Your pricing policy and quote process.
Example: Commercial quotes require an on-site assessment; residential taxes are included.
Common mistakes: Assuming every note will automatically be read by NORA — these are reviewed and configured by our team.
If you are unsure: Leave blank if your pricing is fully covered by the price fields above.

Pricing Authorization

Required

What it means: Your confirmation that the pricing details above are accurate and approved for use in configuring NORA.
What to enter: Check the box only if the prices reflect genuine business approval.
Why we need it: Authorization must be genuine. Checking it does not by itself activate the pricing — submission and activation are separate.
Where to find it: Your owner or pricing manager's sign-off.
Example: (checkbox checked)
Common mistakes: Checking the box without actually having approved the prices with the business owner.
If you are unsure: Do not check it until the prices are confirmed by the person who can approve them.

Safety Guidance Status

Required

What it means: Whether you have approved treatment-specific safety instructions, have some that need review, or need help preparing them.
What to enter: Select Approved, Needs review, or Not available. Do not preselect an answer.
Why we need it: Determines whether the child/pet safety and re-entry fields below are required.
Where to find it: Your approved product-label instructions and treatment safety policies.
Example: Yes, our business has approved treatment-specific safety instructions.
Common mistakes: Selecting 'Approved' without actually having written, approved instructions to provide.
If you are unsure: Select 'Needs review' or 'Not available' — you can still complete onboarding while the safety content is reviewed.

Pet / Child Safety Policy

Conditional

Required when Safety Guidance Status is 'Approved.' Otherwise optional, with a review notice.

What it means: Your approved safety instructions for children, pets, and household occupants.
What to enter: Use your approved product-label instructions and treatment-specific guidance. Do not enter generic assurances that all treatments are safe.
Why we need it: NORA should only relay safety information your business has actually approved for each treatment.
Where to find it: Your product labels, SDS, and treatment-specific safety policies.
Example: Keep children and pets away from treated areas until dry; cover fish tanks before treatment.
Common mistakes: Writing 'all treatments are safe' — a generic assurance that may not be accurate for every product.
If you are unsure: Set Safety Guidance Status to 'Needs review' and we will help prepare the appropriate guidance.

Re-entry Guidance

Conditional

Required when Safety Guidance Status is 'Approved.' Otherwise optional, with a review notice.

What it means: Your approved post-treatment instructions for when people and pets may return.
What to enter: Specify the business-approved timing. Do not insert a default such as 'two hours' — correct timing varies by treatment and product-label instructions.
Why we need it: Accurate re-entry guidance protects customers and reflects your approved product-label instructions.
Where to find it: Your product labels and treatment-specific re-entry policies.
Example: Re-enter once surfaces are dry and the area has been ventilated; timing varies by product.
Common mistakes: Applying a universal 'two hours' to every treatment when product labels differ.
If you are unsure: Set Safety Guidance Status to 'Needs review' rather than inventing a re-entry time.

Emergency Protocol Text

Optional

What it means: Your business-approved emergency and chemical-exposure response instructions.
What to enter: Provide any approved business-specific escalation instructions. Your existing NORA safety protocol remains subject to review before client activation.
Why we need it: Captures your approved escalation steps. This does not replace the standard emergency guidance that life-threatening emergencies require 911 and pesticide exposure requires Poison Control at 1-800-222-1222.
Where to find it: Your emergency response policy and SDS exposure guidance.
Example: For exposure, rinse skin with water and call Poison Control; for reactions, call 911.
Common mistakes: Entering unverified medical treatment instructions. Always direct life-threatening emergencies to 911.
If you are unsure: Leave blank if you do not have approved business-specific escalation steps yet.

Re-service Guarantee

Optional

What it means: The re-service guarantee your business offers, if any.
What to enter: Describe your approved guarantee, including applicable time limits and exclusions. Do not insert a default 30-day guarantee.
Why we need it: Keeps NORA's guarantee statements accurate to what your business actually offers.
Where to find it: Your service agreement and guarantee policy.
Example: Free re-service within 30 days of treatment for active plan customers.
Common mistakes: Implying all services qualify for the same guarantee when terms differ by service.
If you are unsure: Leave blank if you do not have a defined re-service guarantee.

Warranty Details

Optional

What it means: Any distinct termite warranties, recurring-plan terms, exclusions, or conditions your team wants reviewed for NORA's knowledge base.
What to enter: Describe warranties or terms you want reviewed, including exclusions and conditions.
Why we need it: Distinct warranties (e.g., termite warranties) may have different terms than re-service guarantees.
Where to find it: Your termite warranty documents and recurring-plan agreements.
Example: 1-year termite retreatment warranty; excludes new construction and structural changes.
Common mistakes: Confusing the re-service guarantee with a separate termite warranty.
If you are unsure: Leave blank if you have no separate warranty terms to review.

Review Requests Enabled

Required

What it means: Whether you'd like NORA's post-service workflow to request Google reviews.
What to enter: Select Yes, No, or Unsure. Do not preselect.
Why we need it: Determines whether the Google review link is required and whether the review-request workflow should be considered.
Where to find it: Your marketing and reputation-management policy.
Example: Yes
Common mistakes: Selecting Yes without having a real, verifiable Google review link to provide.
If you are unsure: Select 'Unsure' — the review-request preference requires clarification before activation.

Google Review Link

Conditional

Required and validated as HTTPS only when Review Requests Enabled is 'Yes.' Not required for 'No' or 'Unsure.'

What it means: The direct review link for your Google Business Profile.
What to enter: Paste the direct review link. It must be a valid HTTPS URL. A valid URL is not proof it is a genuine Google review link — that is verified separately.
Why we need it: The link must be verified before review-request messages are activated.
Where to find it: Your Google Business Profile → 'Ask for reviews' or your reputation-management tool.
Example: https://g.page/r/your-business-id/review
Common mistakes: Pasting a non-HTTPS link, a homepage URL, or a link to a different platform.
If you are unsure: Set Review Requests to 'Unsure' until the correct Google review link is available.

Scheduling, Capacity & Payments

Captures how appointments are booked, the calendar and capacity you operate with, and how payments are handled so NORA's scheduling and payment behavior matches your real setup.

Scheduling Software

Required

What it means: The scheduling or field-service software your business currently uses.
What to enter: Select your platform — Zeppelynn Calendar, FieldRoutes, GorillaDesk, Jobber, WorkWave, ServiceTitan, PestPac, Other, manual scheduling, or unsure.
Why we need it: Helps us understand your current scheduling process. Selecting a software does not automatically connect it to NORA.
Where to find it: Your office systems and the tool your dispatcher uses daily.
Example: Zeppelynn Calendar
Common mistakes: Selecting a platform you used to use, or assuming the selection connects the integration.
If you are unsure: Select 'Unsure; please review our setup' so we can help you identify the right option.

Other Scheduling Software

Conditional

Appears only when Scheduling Software is 'Other.' It becomes required while 'Other' is selected.

What it means: The name of your scheduling software when it was not in the standard list.
What to enter: Enter the product name you use.
Why we need it: So our team can review whether an integration is available and what setup is required.
Where to find it: Your office systems.
Example: PestPac by WorkWave (legacy)
Common mistakes: Leaving blank while 'Other' is selected, which blocks progression.
If you are unsure: Switch Scheduling Software to 'Unsure' rather than guessing the product name.

Voice Booking Mode

Required

What it means: How NORA should handle appointment requests.
What to enter: Select direct calendar booking, dispatcher callback, or texting an existing booking link.
Why we need it: Each mode has different setup requirements that we review against your actual scheduling setup before activation.
Where to find it: Your booking and dispatch policy.
Example: Book directly into the configured NORA calendar.
Common mistakes: Choosing direct calendar booking when your calendar is not yet set up, or choosing a booking link you do not have.
If you are unsure: Choose dispatcher callback so NORA captures the request for your team to arrange.

Direct Booking Link

Conditional

Required (and validated as HTTPS) only when Voice Booking Mode is 'text booking link.' Optional for the other modes.

What it means: An existing online booking link you'd like NORA to text to callers.
What to enter: Paste a valid HTTPS booking link. A valid URL is not proof the link has been tested or connected — that is confirmed separately.
Why we need it: When you choose the booking-link mode, NORA needs a real link to send.
Where to find it: Your scheduling software's booking-page settings.
Example: https://book.yourbusiness.com
Common mistakes: Entering a non-HTTPS link or an internal admin URL instead of a public booking page.
If you are unsure: Switch to dispatcher callback until you have a verified public booking link.

Bookable Appointment Types

Required

What it means: Which appointment types NORA should help schedule. At least one is required.
What to enter: Select one or more: general pest inspection, termite inspection, re-service, treatment visit, commercial estimate, or other.
Why we need it: Your selections describe the scheduling requirements. Available calendars and booking must be verified during implementation.
Where to find it: Your appointment categories in your scheduling software.
Example: General pest inspection, Treatment appointment
Common mistakes: Assuming selecting an appointment type automatically creates its calendar — it does not. The current NORA configuration includes a General Pest Inspection calendar only.
If you are unsure: Select only the appointment types you can actually fulfill with the current calendar setup.

Other Appointment Type

Conditional

Required only when 'Other' is selected under Bookable Appointment Types.

What it means: A description of an appointment type not in the standard list.
What to enter: Describe the additional appointment type you want NORA to help schedule.
Why we need it: So our team can review the required calendar and booking settings.
Where to find it: Your custom appointment categories.
Example: Bed bug heat treatment consult
Common mistakes: Leaving blank while 'Other' is selected, which blocks progression.
If you are unsure: Unselect 'Other' and use only the standard categories until the custom type is confirmed.

Weekly Operating Hours

Required

What it means: The normal business and appointment hours when your office and service team operate.
What to enter: Enter your actual hours, including any differences between office hours and available appointment times. Preserve line breaks.
Why we need it: These describe booking preferences. NORA is intended to answer inbound calls 24/7 — these hours do not disable call answering.
Where to find it: Your office schedule and booking policy.
Example: Monday–Friday: 8:00 AM–5:00 PM Saturday: 8:00 AM–12:00 PM Sunday: Closed
Common mistakes: Confusing operating hours with when NORA is allowed to answer — NORA answers around the clock regardless.
If you are unsure: Enter your real office hours; our team confirms calendar settings separately.

Number of Field Technicians

Required

What it means: How many field technicians your business currently has.
What to enter: Enter a positive whole number (minimum 1).
Why we need it: A capacity input. It does not infer the number of office employees, and it does not automatically change the existing calendar or its available slots.
Where to find it: Your current staff roster of field technicians.
Example: 4
Common mistakes: Counting office staff, entering zero, or using a decimal. The field rejects zero, negatives, decimals, and non-numeric input.
If you are unsure: Enter the current number of technicians; you can update it later.

Capacity Mode

Required

What it means: How daily appointment capacity should be managed.
What to enter: Select defined daily limit, dispatcher-managed, or needs review. Do not preselect.
Why we need it: Determines whether a daily inspection limit is required and how we configure capacity.
Where to find it: Your dispatch and booking policy.
Example: We have a defined daily inspection limit.
Common mistakes: Selecting a defined limit without then providing the actual daily number.
If you are unsure: Select 'Please recommend an appropriate capacity model.'

Maximum Inspections Per Day

Conditional

Required only when Capacity Mode is 'defined_capacity.' Not required for dispatcher-managed or needs-review modes.

What it means: The total daily inspection limit across all technicians, not the per-technician limit.
What to enter: Enter a positive whole number (minimum 1).
Why we need it: Your total daily inspection limit. We verify the appropriate calendar and capacity settings separately.
Where to find it: Your scheduling capacity policy.
Example: 12
Common mistakes: Entering a per-technician number instead of the total, or using a decimal.
If you are unsure: Switch Capacity Mode to 'needs review' rather than guessing.

Minimum Booking Notice

Required

What it means: How much advance notice is required before an appointment.
What to enter: Select same-day, 24 hours, 48 hours, or needs review. Do not preselect.
Why we need it: A requested scheduling preference. Actual availability and buffer behavior must be confirmed in the configured calendar.
Where to find it: Your booking policy.
Example: At least 24 hours' notice.
Common mistakes: Selecting same-day when your team cannot mobilize that quickly.
If you are unsure: Select 'Please review our scheduling requirements.'

Inspection Buffer

Required

What it means: The buffer allowed between inspection appointments.
What to enter: Select 0, 15, 30, or 45 minutes, or needs review. Do not preselect.
Why we need it: A requested scheduling preference. The actual buffer behavior must be confirmed in the configured calendar.
Where to find it: Your scheduling and travel-time policy.
Example: 30 minutes.
Common mistakes: Selecting no buffer when your technicians need travel time between jobs.
If you are unsure: Select 'Please review our requirements.'

Payment / Deposit Policy

Required

What it means: Whether your business requires a deposit or payment before an appointment.
What to enter: Select no prepayment, secure payment link, full prepayment, other, or needs review. Do not preselect.
Why we need it: Determines whether payment process notes are required and what integration may be needed.
Where to find it: Your payment and booking policy.
Example: No prepayment required; payment is handled under our normal invoicing policy.
Common mistakes: Selecting a payment-link option without describing how customers receive the link. Never enter card numbers or credentials.
If you are unsure: Select 'We need help determining the appropriate configuration.'

Payment Notes

Conditional

Required when the Payment Policy is 'secure payment link,' 'full prepayment,' or 'other.' Not required for 'no prepayment' or 'needs review.'

What it means: A description of the approved payment process for the selected payment option.
What to enter: Describe how customers receive a secure payment link, who verifies payment, and any approved deposit conditions. Do not enter card numbers or payment credentials.
Why we need it: So our team can review the payment process. NORA cannot collect, authorize, or process payments unless a verified secure payment integration has been implemented.
Where to find it: Your payment-processing policy and booking workflow.
Example: We email a Stripe payment link; the office confirms receipt before booking.
Common mistakes: Entering card numbers, CVV, or bank credentials. This form never collects payment credentials.
If you are unsure: Set Payment Policy to 'needs review' and we will help define the appropriate configuration.

Voice, Dispatch & Emergency Contacts

Captures how NORA should sound, who it refers to, how to escalate, and what happens outside your normal operating hours.

Spoken Business Greeting

Required

What it means: The greeting you'd like NORA to use when answering calls.
What to enter: Provide the exact greeting text, up to 500 characters. Do not prefill a demo greeting as an actual value.
Why we need it: We review it against your business identity and the actual Voice AI greeting configuration before activation. It is not applied to the live agent automatically.
Where to find it: Your owner's preferred call script and brand voice.
Example: Thank you for calling [Business Name]. This is Nora. How may I help you today?
Common mistakes: Using a placeholder greeting as the real value, or exceeding 500 characters.
If you are unsure: Use the example as a starting point and adapt it to your business name.

Dispatcher / Office Display Name

Required

What it means: The name NORA should use when referring to your office or dispatch team.
What to enter: Enter the person or team name that coordinates incoming requests (e.g., 'Sarah,' 'Owner,' or 'Front Desk Team').
Why we need it: This is a business-facing display preference. It does not create a CRM user or assign jobs automatically.
Where to find it: Your staff roster and how you introduce your office to callers.
Example: Sarah, Owner
Common mistakes: Entering a generic 'Dispatch' when callers expect a personal name.
If you are unsure: If you manage the office yourself, use 'Owner' or your preferred display name.

Primary Escalation Phone

Required

What it means: The business-approved number for important call alerts and human escalation.
What to enter: Enter a valid US or international phone number with country code. Supports spaces, hyphens, and parentheses.
Why we need it: This is where urgent alerts are routed. We never call or text it from this form, and we do not verify ownership.
Where to find it: Your owner or operations lead's direct line.
Example: +1 650 241 9598
Common mistakes: Using a shared front-desk number that no one monitors for urgent alerts.
If you are unsure: Use the number your owner or operations lead checks throughout the day.

Primary Escalation Email

Required

What it means: The inbox for important NORA alerts.
What to enter: Enter a valid email address monitored by the person responsible for reviewing alerts.
Why we need it: This is configuration information only — it does not update the existing live escalation email automatically.
Where to find it: Your owner or operations lead's monitored inbox.
Example: alerts@yourbusiness.com
Common mistakes: Using a personal email no one checks for business alerts.
If you are unsure: Use the inbox your owner checks at least daily.

Secondary Contact Available

Required

What it means: Whether you have a secondary emergency or on-call contact for backup escalation.
What to enter: Select Yes, No, or Needs review. Do not preselect.
Why we need it: A backup contact helps ensure urgent alerts have a defined escalation path.
Where to find it: Your emergency contact list.
Example: Yes, a backup contact is available.
Common mistakes: Selecting Yes without actually providing a backup number in the next field.
If you are unsure: Select 'We need help defining the backup arrangement' — it shows a non-blocking review notice.

Secondary Emergency Phone

Conditional

Required only when Secondary Contact Available is 'Yes.' Hidden and not required for 'No' or 'Needs review.'

What it means: The backup on-call phone number for urgent escalation.
What to enter: Enter a valid US or international number using the same validation as the primary escalation phone.
Why we need it: Gives NORA a defined backup path. We do not implement an automatic backup-call cascade — that would require separate, verified workflow configuration.
Where to find it: Your backup on-call contact's number.
Example: +1 623 555 0119
Common mistakes: Entering the same number as the primary, which defeats the backup purpose.
If you are unsure: Set Secondary Contact Available to 'Needs review' rather than inventing a backup number.

Language Preference

Required

What it means: Which language experience you'd like NORA to support.
What to enter: Select English only, English and Spanish, or primarily Spanish. Do not preselect.
Why we need it: Additional language capability may require separate Voice AI configuration and testing. Selecting a language does not enable multilingual answering automatically.
Where to find it: Your caller demographic and staffing capacity.
Example: English only.
Common mistakes: Selecting Spanish support without confirming your team can respond in Spanish.
If you are unsure: Select 'English only' for now; additional language configuration can be reviewed separately.

Human Escalation Triggers

Required

What it means: The situations in which NORA should involve a human from your team. At least one is required.
What to enter: Select one or more triggers: caller requests a human, billing or complaint, cancellation or exception, commercial estimate, out-of-scope or uncertain, urgent service request, safety follow-up, or other.
Why we need it: These describe normal business escalation. They do not replace NORA's emergency safety protocol.
Where to find it: Your dispatch and customer-service policy.
Example: The caller explicitly requests a person; Billing disputes or customer complaints.
Common mistakes: Selecting so many triggers that nearly every call escalates, defeating the automation.
If you are unsure: Keep the default common triggers and adjust with our team during implementation.

Other Human Escalation Trigger

Conditional

Required only when 'Other' is selected under Human Escalation Triggers.

What it means: A description of the other situations that require human involvement.
What to enter: Describe the business-specific situations in plain language.
Why we need it: So our team can review whether additional workflow changes are needed.
Where to find it: Your dispatch and escalation policy.
Example: Any call about a pet exposure during a treatment requires an owner call-back.
Common mistakes: Leaving blank while 'Other' is selected, which blocks progression.
If you are unsure: Unselect 'Other' and use only the standard triggers until confirmed.

After-Hours Strategy

Required

What it means: How NORA should handle calls that require follow-up outside your normal operating hours.
What to enter: Select next-business-day callback, on-call notification, callback and on-call, or needs review. Do not preselect.
Why we need it: NORA is intended to answer inbound calls 24/7. This describes how after-hours requests are handled, not when the agent is allowed to answer.
Where to find it: Your after-hours coverage policy.
Example: Capture the request and arrange follow-up on the next business day.
Common mistakes: Selecting an on-call strategy without a backup contact set up, or assuming NORA will stop answering after hours.
If you are unsure: Select 'Help us determine the appropriate after-hours arrangement.'

A2P & Messaging Compliance

Captures your messaging-registration readiness, intended SMS categories, consent practices, and policy URLs so messaging is reviewed — not activated — before deployment.

SMS Registration Status

Required

What it means: Your current SMS (A2P 10DLC) registration status, as you understand it. This is client-reported, not independently verified.
What to enter: Select approved, pending, not started, or unsure. Do not preselect.
Why we need it: We review the applicable registration requirements and determine what steps remain before SMS workflows can be activated. Selecting a status does not register your business.
Where to find it: Your messaging provider or CRM admin's campaign records.
Example: Registration has been submitted and is pending.
Common mistakes: Selecting 'Approved' without confirmation, or assuming the form itself registers your business.
If you are unsure: Select 'I'm not sure about the current status' — we will review the requirements with you.

SMS Categories

Required

What it means: Which customer-facing SMS messages you'd like NORA to support. At least one is required.
What to enter: Select one or more categories, or the exclusive 'no SMS at launch' or 'unsure' options.
Why we need it: We verify the corresponding workflow, consent approach, registration, and delivery configuration support each category before activation.
Where to find it: Your current SMS campaigns and messaging use cases.
Example: Appointment confirmations, Appointment reminders
Common mistakes: Selecting specific categories and 'no SMS at launch' together — they are mutually exclusive.
If you are unsure: Select 'Please help us determine which messages are appropriate.'

Other SMS Categories

Conditional

Required only when 'Other' is selected under SMS Categories.

What it means: A description of other customer-facing SMS use cases.
What to enter: Describe each additional customer SMS use case in plain language.
Why we need it: So our team can review the corresponding workflow and registration.
Where to find it: Your current SMS campaigns.
Example: Seasonal treatment reminder campaigns tied to active quarterly plans.
Common mistakes: Describing internal dispatcher alerts as customer SMS — internal alerts are not customer-facing messages.
If you are unsure: Unselect 'Other' and use only the standard categories until your use case is confirmed.

SMS Consent Methods

Required

What it means: How customers currently agree to receive text messages from your business. At least one is required.
What to enter: Select one or more established methods, or the exclusive 'not established' or 'unsure' options.
Why we need it: An appropriate consent process must be established and reviewed before applicable SMS is activated.
Where to find it: Your intake forms, booking flow, and service agreements.
Example: A website form with an SMS consent checkbox.
Common mistakes: Assuming that having a customer's phone number alone establishes consent — it does not.
If you are unsure: Select 'We do not yet have a defined SMS consent process' or 'We need help reviewing our consent process.'

Other Consent Method

Conditional

Required only when 'Other' is selected under SMS Consent Methods.

What it means: A description of another documented consent method.
What to enter: Describe the alternative consent method in plain language.
Why we need it: So our team can review whether it meets carrier and consent requirements.
Where to find it: Your intake and consent-capture processes.
Example: Customers initial a consent line on the printed service agreement at the first visit.
Common mistakes: Describing a general acknowledgment of the survey as customer consent — that is not consent.
If you are unsure: Switch SMS Consent Methods to 'not established' or 'unsure' rather than guessing.

Public Website URL

Optional

What it means: Your public business website, if you have one.
What to enter: Enter a valid HTTPS URL, or leave blank if you do not have a website.
Why we need it: Identifies where customers learn about your business.
Where to find it: Your website address.
Example: https://yourbusiness.com
Common mistakes: Entering a non-HTTPS or internal/staging URL.
If you are unsure: Leave blank if you do not have a public website.

SMS Opt-In Page URL

Conditional

Required when SMS Consent Methods includes 'website form' or 'online booking.' Otherwise optional.

What it means: The website page where customers are asked to opt in to SMS.
What to enter: Enter a valid HTTPS URL for the page where consent is captured. A valid URL is not proof its consent mechanism is compliant — that is reviewed separately.
Why we need it: If you select a website-based consent method, the relevant opt-in page must be provided or the consent method corrected.
Where to find it: Your website's SMS or contact preferences page.
Example: https://yourbusiness.com/preferences
Common mistakes: Selecting a website consent method but leaving this URL blank blocks progression until supplied or corrected.
If you are unsure: Switch to an accurate consent method, or select 'not established' and we will help.

Privacy Policy URL

Optional

What it means: Your public privacy policy URL, recommended where you have a public website.
What to enter: Enter a valid HTTPS URL if available. If missing, a non-blocking readiness notice appears for review.
Why we need it: Registration or launch processes may require a privacy policy. We do not claim its content meets requirements without reviewing it.
Where to find it: Your website footer or legal pages.
Example: https://yourbusiness.com/privacy
Common mistakes: Entering a non-HTTPS or broken link.
If you are unsure: Leave blank; we flag it for manual review if needed.

Terms & Conditions URL

Optional

What it means: Your SMS terms and conditions URL, where applicable.
What to enter: Enter a valid HTTPS URL if available.
Why we need it: Some messaging use cases require additional disclosures or terms, which are flagged for review if missing.
Where to find it: Your website legal pages.
Example: https://yourbusiness.com/sms-terms
Common mistakes: Pasting a non-HTTPS URL.
If you are unsure: Leave blank if you do not have dedicated SMS terms.

Consent Disclosure

Optional

What it means: The exact wording customers see or hear when asked to agree to SMS.
What to enter: Paste your existing disclosure wording for review. If none exists, leave blank so an appropriate process can be discussed.
Why we need it: We review it for carrier and compliance relevance. Do not generate consent claims on your behalf.
Where to find it: Your opt-in form, service agreement, or IVR script.
Example: By providing your number, you consent to receive text messages about your appointments. Reply STOP to cancel.
Common mistakes: Asserting that an existing disclosure meets carrier or legal requirements without a separate review.
If you are unsure: Leave blank and we will help draft appropriate disclosure language.

Sample Confirmation SMS

Optional

What it means: An example of the appointment confirmation message you'd like to send.
What to enter: Paste your preferred confirmation message, if available.
Why we need it: Sample messages are reviewed before production activation. Collecting a sample does not authorize or launch it.
Where to find it: Your current SMS templates.
Example: Your pest inspection is confirmed for Tue 10am. Reply C to confirm or R to reschedule.
Common mistakes: Including real customer phone numbers or personal data in the sample.
If you are unsure: Leave blank if you do not have a template yet.

Sample Reminder SMS

Optional

What it means: An example of the appointment reminder message you'd like to send.
What to enter: Paste your preferred reminder message, if available.
Why we need it: Reviewed before activation; does not authorize sending by itself.
Where to find it: Your current SMS templates.
Example: Reminder: your appointment is tomorrow at 10am. See you then!
Common mistakes: Including personal customer data in the sample.
If you are unsure: Leave blank if you do not have a template yet.

Sample Follow-Up SMS

Optional

What it means: An example follow-up message you'd like to send after service.
What to enter: Paste an example follow-up message, if applicable.
Why we need it: Reviewed before activation; does not authorize sending by itself.
Where to find it: Your current SMS templates.
Example: Thanks for choosing us! If you have any issues, reply here or call us. We'll follow up.
Common mistakes: Including personal customer data or unverified promotional claims.
If you are unsure: Leave blank if you do not have a template yet.

Additional SMS Notes

Optional

What it means: Any relevant timing preferences, message categories, consent-recording methods, or special restrictions.
What to enter: Describe additional details about your SMS program. Do not include real customer phone numbers, message histories with personal information, passwords, or payment information.
Why we need it: Provides context our team reviews before activation.
Where to find it: Your messaging program documentation.
Example: No messages after 8pm local time; STOP requests handled within 24 hours.
Common mistakes: Including customer PII or credentials in this notes field.
If you are unsure: Leave blank if no additional details apply.

Telephony & Call Routing

Captures your telephony preferences — new number, forwarding, or porting — and your SMS sending-line strategy for review. Nothing is provisioned, forwarded, ported, or activated by submitting this form.

Telephony Strategy

Required

What it means: How you'd like calls to reach NORA — a new local number, forwarding your existing number, or exploring porting your number.
What to enter: Select new local number, forward existing, port existing, or needs review. Do not preselect.
Why we need it: We review your current setup and confirm implementation steps. Selecting an option does not initiate provisioning, forwarding, or porting.
Where to find it: Your owner or telecom admin's preferred approach.
Example: Provision a new local business number for NORA.
Common mistakes: Selecting porting without understanding it is a separate authorization process.
If you are unsure: Select 'Help us determine the best option.'

Existing Office Number

Conditional

Required only when Telephony Strategy is 'forward existing number' or 'port existing number.' Optional otherwise.

What it means: The current public-facing number customers call today.
What to enter: Enter a valid US or international number using the same phone validation as the rest of the form.
Why we need it: We verify ownership and compatibility separately. We do not call, text, port, or forward this number from the form.
Where to find it: Your business phone bill, signage, and website contact page.
Example: +1 623 555 0188
Common mistakes: Entering a private mobile number instead of the public business line.
If you are unsure: If you are not sure which number to use, switch the strategy to 'needs review.'

Current Phone Carrier

Conditional

Required only when Telephony Strategy is 'forward existing number' or 'port existing number.' Optional for a new number.

What it means: Who currently provides your business phone service.
What to enter: Select your carrier, or 'Other' or 'Unsure' if applicable. Do not preselect.
Why we need it: Carrier information helps us review forwarding or porting feasibility with your current provider.
Where to find it: Your phone bill or telecom admin.
Example: Comcast / Xfinity
Common mistakes: Guessing the carrier when you are unsure.
If you are unsure: Select 'Unsure' — a non-blocking review notice appears; you can still complete onboarding.

Other Phone Carrier

Conditional

Required only when an existing-number strategy is chosen and the carrier is 'Other.'

What it means: The name of your current telephone provider when it was not in the standard list.
What to enter: Enter the provider name.
Why we need it: So our team can review whether forwarding or porting is supported.
Where to find it: Your phone bill or telecom admin.
Example: Cox Business
Common mistakes: Leaving blank while 'Other' is selected, which blocks progression.
If you are unsure: Switch Current Phone Carrier to 'Unsure' rather than guessing.

Preferred Area Code

Optional

Displayed only when Telephony Strategy is 'new local number.'

What it means: A preferred three-digit US area code for the new number, if known.
What to enter: Enter a three-digit area code. If supplied, it must be a valid format. We do not promise a specific number is available.
Why we need it: A preference only, not a reservation. We check availability before provisioning. We never infer it from your browser, IP, or timezone.
Where to find it: The area code of your service region.
Example: 619
Common mistakes: Entering alphabetic or clearly malformed values.
If you are unsure: Leave blank and we will recommend an area code based on your service area.

Call Forwarding Readiness

Conditional

Required only when Telephony Strategy is 'forward existing number.' Not required for other strategies.

What it means: Whether your team or your provider can configure call forwarding on the existing number.
What to enter: Select can configure, carrier assistance, or unsure.
Why we need it: We do not provide provider-specific instructions until the carrier and phone-system configuration are confirmed.
Where to find it: Your telecom admin or phone-system settings.
Example: Yes, we can configure forwarding ourselves.
Common mistakes: Selecting 'we can configure' without checking who has access to the phone system.
If you are unsure: Select 'We are not sure' — a non-blocking setup-review notice appears.

SMS Sending Line Strategy

Required

What it means: How you'd prefer to handle the phone number used for customer-facing SMS messages.
What to enter: Select a dedicated local SMS number, using your existing number if eligible, hosted SMS on your landline if supported, no SMS at launch, or needs review. Do not preselect.
Why we need it: The right messaging number depends on eligibility, your telephony approach, registration status, and platform support. No SMS line is activated by submitting this survey.
Where to find it: Your messaging provider and telecom admin.
Example: Use a dedicated local SMS-capable number.
Common mistakes: Selecting an SMS-enabled line while choosing 'no SMS at launch' on the messaging slide — a non-blocking consistency notice appears.
If you are unsure: Select 'Help us determine the appropriate arrangement.'

Hosted SMS Documentation Available

Conditional

Required only when the SMS Sending Line Strategy is 'hosted SMS on existing landline.'

What it means: Whether you can provide evidence that you own or control the existing landline through the appropriate secure process.
What to enter: Select Yes, No, or Unsure.
Why we need it: Hosted SMS eligibility and evidence are reviewed separately. This form does not collect a phone bill or identity documents.
Where to find it: Your telecom account ownership records.
Example: Yes, we can provide the necessary documentation.
Common mistakes: Assuming selecting 'Yes' uploads or proves documentation — it does not. A separate secure process is arranged after review.
If you are unsure: Select 'We need guidance on what is required' — a non-blocking review notice appears.

Telephony Notes

Optional

What it means: Additional details about your current office line, phone system, forwarding constraints, or preferred local presence.
What to enter: Describe relevant details. Do not include carrier account PINs, passwords, authentication codes, or account credentials.
Why we need it: Provides context for our telephony review.
Where to find it: Your telecom admin or phone-system documentation.
Example: Our main line has an IVR; forwarding to NORA should bypass the menu.
Common mistakes: Entering account credentials or PINs — never put credentials in this form.
If you are unsure: Leave blank if no additional details apply.

Telephony Review Acknowledged

Required

What it means: Your confirmation that you understand these selections describe preferences for implementation review only.
What to enter: Check the box to confirm. It confirms understanding only — it does not authorize porting or replace any carrier authorization process.
Why we need it: Required for progression so the client understands no number is provisioned, ported, forwarded, or activated solely by completing the survey.
Where to find it: Your authorized representative.
Example: (checkbox checked)
Common mistakes: Checking without reading the acknowledgment.
If you are unsure: Do not check it until you understand and agree with the statement.

Final Review & Authorization

Captures your target go-live date and the authorized signer's acknowledgments so the configuration is ready for review — not activated.

Target Go-Live Date

Required

What it means: Your preferred target date for NORA to go live.
What to enter: Select a future date. Past and invalid dates are rejected. The date is kept when you navigate away and back.
Why we need it: A planning input only. The actual activation date depends on configuration, registrations, testing, and outstanding review items. We do not create an appointment or calendar event for this date.
Where to find it: Your owner's preferred launch timeline.
Example: 2026-12-01
Common mistakes: Selecting a past date, or assuming the date guarantees activation.
If you are unsure: Choose a realistic future date; it can be adjusted later. We do not promise that date.

Authorized Signer Attestation

Required

What it means: Your confirmation that you are authorized to provide this information for the business and that it is accurate to the best of your knowledge.
What to enter: Check the box only if the statement is true.
Why we need it: Confirms the person submitting the form has the authority to represent the business in this configuration.
Where to find it: Your role and authorization at the business.
Example: (checkbox checked)
Common mistakes: Checking it when you are not actually authorized to approve the configuration.
If you are unsure: Do not check it — have the authorized owner or manager complete the final review instead.

Pesticide Safety Acknowledgment

Required

What it means: Your understanding that NORA's service scope, prices, safety answers, treatment instructions, booking rules, and emergency handling must be reviewed and configured appropriately before activation.
What to enter: Check the box to confirm you understand that general onboarding answers do not override treatment-specific product-label instructions or emergency protocols.
Why we need it: Reinforces that safety and operational scope are reviewed separately before activation.
Where to find it: Your safety and operational policies.
Example: (checkbox checked)
Common mistakes: Checking it while expecting onboarding answers to override product-label or emergency requirements.
If you are unsure: Do not check it until you understand and agree with the statement.

Configuration Authorization

Required

What it means: Your authorization for Zeppelynn AI to use the information provided to prepare the proposed NORA configuration for review.
What to enter: Check the box to confirm you understand that completing the form does not automatically activate NORA, register SMS, submit a carrier campaign, create calendars, connect an integration, charge a payment method, forward calls, or port a number.
Why we need it: Confirms the client understands the form prepares a configuration for review; it does not perform any of those activation actions.
Where to find it: Your authorized representative.
Example: (checkbox checked)
Common mistakes: Checking it while expecting the form itself to activate NORA or send messages.
If you are unsure: Do not check it until you understand and agree with the statement.

Authorized Signer Name

Required

What it means: The full name of the authorized representative confirming these details.
What to enter: Enter your full name. Whitespace-only values are rejected.
Why we need it: A typed name for the onboarding confirmation screen. It is not described as a cryptographically verified signature, and it alone does not constitute a legally valid electronic signature.
Where to find it: Your legal name as the authorized representative.
Example: Jordan Rivera
Common mistakes: Entering a nickname or leaving it blank, which blocks progression.
If you are unsure: Use your full legal name as the authorized representative.

Security, Scope & Safety

Accurate answers help prevent incorrect configuration and implementation delays. Use the most current information available.
Selecting a service or feature does not prove it is licensed, integrated, approved, or available for deployment.
Pest-control safety procedures must reflect your business's approved policies and applicable product-label and regulatory requirements — not generic assurances.
Fumigation, specialized wildlife work, and other scope-sensitive services may require clarification; this form does not invent an approval or blocking workflow.
SMS consent, carrier registration, and messaging activation are separate considerations. A self-reported status is not independent verification.
Existing phone numbers and telephone services are not changed merely by submitting this onboarding form.
This guide is informational and is not a substitute for legal, licensing, carrier, or pesticide-safety advice.

After You Submit

Your completed answers are saved for Zeppelynn AI's team to review. The displayed submission reference helps us identify your record.
Your submission remains pending review until the applicable configuration, safety, registration, and operational checks take place.
Submitting the form does not by itself activate NORA, a phone number, SMS messaging, a calendar integration, a payment integration, or any workflow.
Zeppelynn AI may need to clarify answers — especially pricing, safety guidance, scope-sensitive services, and telephony — before configuration proceeds.
A target go-live date is a planning input. We do not guarantee activation on that date, and we do not create a calendar event for it.
No unverified turnaround time, launch date, or approval is promised by completing the questionnaire.

Frequently Asked Questions

What should I prepare before starting the form?

Review the Before You Start checklist above. The most common delay is not having approved prices, safety guidance, or your current telephony details on hand. Choose 'Unsure' or 'Needs review' when a field offers it rather than guessing.

What do I do when I don't know an answer?

If a field offers an 'Unsure' or 'Needs review' option, use it — you can still complete onboarding while that area is reviewed. For optional fields, leave them blank. For anything blocking, contact Zeppelynn AI before submitting.

Do my pricing and policies need to be real, or can I estimate?

Use your actual approved prices, plans, warranties, and safety guidance. Estimates or demo values cause configuration errors and may require re-submission. Pricing authorization must reflect genuine business approval.

What does the submission reference mean?

It's the unique identifier for your saved onboarding record. It does not mean NORA has been activated or that your answers have been reviewed or approved. Share it with us if you have follow-up questions.

Does submitting the form activate NORA?

No. Submission saves your answers for review. Activation requires separate configuration, testing, and — for messaging and telephony — applicable registration, consent, and carrier processes.

When can SMS messaging or telephone services be enabled?

Only after the relevant registration, consent, carrier, and platform reviews are complete. Selecting an SMS category or telephony strategy here records a preference; it does not enable the capability.

Why does the form ask about tax ID availability but not the number itself?

We need to know whether a business tax identifier exists for planning, but the identifier itself is sensitive and should not be entered in this survey. Never paste an EIN, SSN, password, or PIN into any field here.

What if my business performs structural fumigation or specialized wildlife work?

Those services may require additional configuration and safety review. Answering Yes or Unsure to either scope question routes you to a manual scope-review screen that preserves all your answers while we review the relevant scope and booking rules.