Every setting explained

Use this reference with the screen in front of you. For each control, read what it means, the exact value/example, why it matters, its effect, a common mistake and how to check the result. A default is a starting value for a new account/form, not a recommendation for every business or proof of your saved setting.

For example, service Avg time (min) is the time spent doing one customer's work, not their waiting time. That service-editor field is taught in Chapter 5 of the complete manual. Slot Interval, Minimum Lead Time, revisit days and TV slide duration each measure something different; their entries below explain the difference.

Only change a setting when you understand the example and can check the outcome. Start with one change at a time. Server-only automation values are explained in the Smart ETA guide, not presented as imaginary Merchant buttons.

Searchable settings index

S01. Shop name

Where / who: Merchant > Account > Shop Profile > Edit Profile. Merchant owner.

What it means: Name customers and staff use to identify this business.

What exactly to enter or choose: Enter the customer-facing trading name, for example Sharma Family Clinic, as it appears at reception.

Why it matters / effect: Customers need to recognise the business they have opened; a clear shop name helps prevent taking a token for the wrong premises.

Options and starting value: Business text; required by setup. Starting value: Account-specific; no single prefilled business value.

How to save: Open Edit Profile, update Shop name, save the form and reopen it.

Common mistake: Entering the owner's personal name here when the clinic has a different public name.

Check the result: Reopen the profile and check the business name on a fresh customer QR page.

Boundaries: The public shop name is separate from legal billing identity and does not change login ownership. Plan/access dependency: Active merchant account.

S02. Owner name

Where / who: Merchant > Account > Shop Profile > Edit Profile. Merchant owner.

What it means: Identifies the responsible business owner.

What exactly to enter or choose: Enter the responsible owner's name, for example Asha Sharma; use Shop name separately for the clinic name.

Why it matters / effect: This identifies the person responsible for the account; it does not give another person staff access.

Options and starting value: Name, not a staff login role. Starting value: Account-specific; no single prefilled business value.

How to save: Open Edit Profile, update Owner name, save the form and reopen it.

Common mistake: Treating a name change as a transfer of the registered mobile login.

Check the result: Save, reopen the profile and separately check the registered contact details.

Boundaries: Editing this text does not change the registered mobile, verified contacts or access permissions. Plan/access dependency: Active merchant account.

S03. GST number

Where / who: Merchant > Account > Shop Profile > Edit Profile. Merchant owner.

What it means: Business tax identity in the profile.

What exactly to enter or choose: Enter your business's valid GSTIN if registered; leave blank when not applicable.

Why it matters / effect: This records profile tax identity. Invoice billing details have their own GSTIN field and must also be checked.

Options and starting value: Optional valid GSTIN; use billing details separately for InCue invoices. Starting value: Account-specific; no single prefilled business value.

How to save: Open Edit Profile, update GST number, save the form and reopen it.

Common mistake: Copying a customer's GSTIN, inventing a number or assuming this alone updates every invoice.

Check the result: Compare with your own registration and review billing details before buying a plan.

Boundaries: The profile GST field is separate from Subscription & Billing details; an already issued invoice is not rewritten by this edit. Plan/access dependency: Active merchant account.

S04. Business category / Business type

Where / who: Merchant > Account > Shop Profile > Edit Profile. Merchant owner.

What it means: Classifies the business.

What exactly to enter or choose: Choose the closest offered category and subtype, such as Clinic and the relevant clinic type.

Why it matters / effect: It describes the business; you must still create the services, prices and staff separately.

Options and starting value: Choose the categories and types returned by the selector. Starting value: Account-specific; no single prefilled business value.

How to save: Open Edit Profile, update Business category / Business type, save the form and reopen it.

Common mistake: Assuming selecting Clinic automatically creates Consultation or medical permissions.

Check the result: Save the selected category, then confirm your Services list independently.

Boundaries: Category selection does not create services, staff, tax registration or additional permissions. Plan/access dependency: Active merchant account.

S05. Street / area

Where / who: Merchant > Account > Shop Profile > Edit Profile. Merchant owner.

What it means: Physical premises address.

What exactly to enter or choose: Enter the building, floor, street and locality where customers actually attend.

Why it matters / effect: A useful address helps people reach the right reception; it is separate from the coordinates used by location restrictions.

Options and starting value: Address text. Starting value: Account-specific; no single prefilled business value.

How to save: Open Edit Profile, update Street / area, save the form and reopen it.

Common mistake: Using only a city name or the owner's home address for a different premises.

Check the result: Read it as a first-time visitor: could they find this reception?

Boundaries: A written address does not set precise GPS coordinates or replace the separate invoice billing address. Plan/access dependency: Active merchant account.

S06. Pincode

Where / who: Merchant > Account > Shop Profile > Edit Profile. Merchant owner.

What it means: Helps resolve city/state.

What exactly to enter or choose: Enter the six-digit postal PIN of the business premises.

Why it matters / effect: PIN lookup can help fill city/state. A postal area's centre is not the precise building location.

Options and starting value: Valid Indian postal code accepted by the form. Starting value: Account-specific; no single prefilled business value.

How to save: Open Edit Profile, update Pincode, save the form and reopen it.

Common mistake: Entering a customer's PIN or treating a successful PIN lookup as GPS verification.

Check the result: Check the resolved city/state and capture precise business coordinates if nearby-only QR is enabled.

Boundaries: A postal-area lookup can be approximate; use the actual premises GPS separately for nearby-only QR. Plan/access dependency: Active merchant account.

S07. City / State

Where / who: Merchant > Account > Shop Profile > Edit Profile. Merchant owner.

What it means: Location text for the business.

What exactly to enter or choose: Confirm the actual city and state, correcting the offered value where editable.

Why it matters / effect: Location text should match the premises and other profile information.

Options and starting value: Auto-detected from PIN where available; verify the displayed result. Starting value: Account-specific; no single prefilled business value.

How to save: Open Edit Profile, update City / State, save the form and reopen it.

Common mistake: Accepting an incorrect auto-filled city because the PIN was mistyped.

Check the result: Reopen the saved profile and compare with the premises address.

Boundaries: City/state text is separate from exact coordinates and the purchaser details used for billing. Plan/access dependency: Active merchant account.

S08. Latitude / Longitude

Where / who: Merchant > Account > Shop Profile > Edit Profile. Merchant owner.

What it means: Exact business location for location-restricted QR.

What exactly to enter or choose: Use Get current location while physically at reception, or enter verified latitude/longitude for that premises.

Why it matters / effect: Nearby-only QR compares a customer's location with these coordinates. A wrong pin can block genuine customers.

Options and starting value: Valid geographic coordinates or Get current location. Starting value: Account-specific; no single prefilled business value.

How to save: Open Edit Profile, update Latitude / Longitude, save the form and reopen it.

Common mistake: Capturing GPS at home, swapping latitude with longitude or using a postal centroid.

Check the result: With the owner's permission, test a customer phone at reception after enabling location checks.

Boundaries: Location permission and GPS accuracy are device-dependent; a postal PIN centroid is not exact premises GPS. Plan/access dependency: Active merchant account.

S09. Auto-complete on next

Where / who: Merchant > Account > Settings > Queue Configuration. Merchant owner.

What it means: Closes eligible earlier service work when advancing next work.

What exactly to enter or choose: Leave off for explicit Start and Complete handling; turn on only when advancing really means the previous work is finished.

Why it matters / effect: In the supported reception flow, Call Next can close previous active work. It changes records, not just the screen.

Options and starting value: On / Off Starting value: Off in backend model; existing account can differ.

How to save: Change the switch and Save changes.

Common mistake: Turning it on to improve ETA, or pressing Next while the previous customer's work/payment is unfinished.

Check the result: Use an agreed sample flow and inspect which prior token closes; Counter mode has separate capacity rules.

Boundaries: Use only after a staff trial; do not confuse with a background completion timer. Plan/access dependency: Growth/Pro default capability.

S10. Accept walk-ins

Where / who: Merchant > Account > Settings > Queue Configuration. Merchant owner.

What it means: Allows normal walk-in/QR intake under applicable availability rules.

What exactly to enter or choose: Turn on while accepting new walk-ins; turn off when you want to stop intake.

Why it matters / effect: Intake is the ability to create new visits. It is different from Pause, which concerns operating the existing queue.

Options and starting value: On / Off Starting value: On

How to save: Change the switch and Save changes.

Common mistake: Closing intake and assuming it cancels waiting tokens, or using it instead of updating business hours.

Check the result: Open a fresh public QR page and separately inspect existing waiting visits.

Boundaries: Not a refund or queue-close action; staff operational exceptions can differ. Plan/access dependency: Active merchant account.

S11. Concurrent counters

Where / who: Merchant > Account > Settings > Basic Configuration. Merchant owner.

What it means: Specifies simultaneous service capacity.

What exactly to enter or choose: Enter the real simultaneous serving capacity: 1 for one worker, 2 only if two customers can genuinely be served at once.

Why it matters / effect: Parallel capacity affects call limits and estimates. Service-mapped active counters also influence Smart ETA.

Options and starting value: 1-20 in the current app control; plan validation applies. Starting value: 1

How to save: Use minus/plus and Save changes.

Common mistake: Entering the number of chairs, rooms or employees when only one person is actually serving.

Check the result: Compare a controlled one-counter and two-counter workflow; check actual staff availability and mappings.

Boundaries: Does not create staff accounts, named counters or display seats. Plan/access dependency: Multi-counter capability; default Growth/Pro.

S12. Assignment mode

Where / who: Merchant > Account > Settings > Basic Configuration. Merchant owner.

What it means: Chooses how compatible counter work is assigned.

What exactly to enter or choose: Choose Manual when reception decides when to call; choose Auto only when compatible free counters should receive waiting work automatically.

Why it matters / effect: Auto assignment claims an available counter and calls eligible work. It does not start or complete the physical service.

Options and starting value: Manual / Auto Starting value: Manual

How to save: Choose the dropdown option and Save changes.

Common mistake: Assuming Auto ignores paused/offline staff or matches a counter that cannot perform all selected services.

Check the result: Check the assigned counter, Called status and TV update before allowing unattended operation.

Boundaries: Auto cannot make an offline, busy or unqualified person available. Plan/access dependency: Multi-counter/assignment entitlement and configured staff.

S13. Daily limit for online tokens

Where / who: Merchant > Account > Settings > QR tokens & revisits. Merchant owner.

What it means: Caps public issuance against the total daily issued count.

What exactly to enter or choose: Enter 100 for a daily intake ceiling of 100 issued tokens, or 0 for no QR daily ceiling.

Why it matters / effect: All issued tokens contribute, including staff issues and appointment conversions; at the threshold new QR issuance stops, while authorised staff can continue.

Options and starting value: Whole number 0-100000; 0 means unlimited. Starting value: 0

How to save: Enter the limit and Save changes; test a public availability page.

Common mistake: Thinking the cap counts only QR tokens or that cancelling a token restores an issued number.

Check the result: At total 98 with limit 100, two ordinary new QR issues can reach the cap; check paid reservations separately.

Boundaries: Includes staff/conversion issue count; cancellations do not reduce it; payment holds/accepted payments affect capacity. Plan/access dependency: Active merchant account.

S14. Token payment refund policy

Where / who: Merchant > Account > Settings > QR tokens & revisits. Merchant owner.

What it means: Discloses your policy before QR submission.

What exactly to enter or choose: Choose the offered policy that describes your real refund terms; explain conditions in Customer terms.

Why it matters / effect: This tells the customer the policy before payment. It does not instruct the gateway to send money back.

Options and starting value: Contact reception for refunds / Refundable as per terms / Non-refundable Starting value: Contact reception for refunds

How to save: Choose the policy and Save changes.

Common mistake: Selecting Refundable and assuming a cancellation automatically refunds the bank payment.

Check the result: Read a fresh QR checkout disclosure and confirm the provider refund procedure with the responsible person.

Boundaries: This does not issue a gateway refund or override applicable obligations. Plan/access dependency: Active merchant account.

S15. Customer terms

Where / who: Merchant > Account > Settings > QR tokens & revisits. Merchant owner.

What it means: Shows arrival, cancellation and refund instructions.

What exactly to enter or choose: Write short customer instructions, for example arrive at reception before your turn, and state your actual refund conditions.

Why it matters / effect: Customers can understand the service terms before taking a token; terms are not executable queue rules.

Options and starting value: Text, maximum 2000 characters. Starting value: Empty

How to save: Enter clear business terms and Save changes.

Common mistake: Putting an OTP, gateway secret, unsupported promise or hidden charge in the text.

Check the result: Read it on a phone and verify it agrees with prices, revisit settings and the refund policy.

Boundaries: Do not collect secrets or customer medical details here; it is not a universal legal template. Plan/access dependency: Active merchant account.

S16. Free revisits

Where / who: Merchant > Account > Settings > QR tokens & revisits. Merchant owner.

What it means: Enables eligible earlier-service fee waivers.

What exactly to enter or choose: Enable only if your business offers free follow-ups; then set days, allowed count and the validity basis.

Why it matters / effect: The system checks matching customer identity and earlier eligible services to calculate a waiver.

Options and starting value: On / Off Starting value: Off

How to save: Turn on, configure days/count/basis and Save changes.

Common mistake: Telling every repeat visitor the visit is free without checking the quoted eligibility.

Check the result: Try a matching eligible sample and a new-service sample; verify waived versus payable amounts.

Boundaries: Same merchant, matching name/mobile and eligible original charges required. New services/upgrades remain payable. Plan/access dependency: Active merchant account.

S17. Valid for (days)

Where / who: Merchant > Account > Settings > QR tokens & revisits. Merchant owner.

What it means: Sets the return window.

What exactly to enter or choose: Enter 7 for a seven-day revisit window; choose another allowed value only if that is your real policy.

Why it matters / effect: The chosen basis visit starts the eligibility window. Increasing days makes more past visits potentially eligible.

Options and starting value: Whole number 1-90 Starting value: 7

How to save: Enable Free revisits, enter days and Save changes.

Common mistake: Entering 7 because it is the default when your actual promise is three days.

Check the result: Read the displayed quote and the qualifying visit's date before confirming a free revisit.

Boundaries: Time-window rules still require qualifying original service/payment records. Plan/access dependency: Active merchant account.

S18. Free revisits (count)

Where / who: Merchant > Account > Settings > QR tokens & revisits. Merchant owner.

What it means: Limits free returns against an original visit.

What exactly to enter or choose: Enter 1 for one free revisit per qualifying allowance, or your intended permitted count.

Why it matters / effect: This limits how many free follow-ups can consume the benefit; it is not the number of services free on a visit.

Options and starting value: Whole number 1-20 Starting value: 1

How to save: Enter the count while Free revisits is on, then Save changes.

Common mistake: Assuming a cancelled/no-show free token always returns the allowance.

Check the result: Review the earlier visits and the current waiver; escalate a disputed allowance instead of creating duplicates.

Boundaries: Cancelling/no-show does not automatically restore it; moving the time basis does not reset the count. Plan/access dependency: Active merchant account.

S19. Count validity from

Where / who: Merchant > Account > Settings > QR tokens & revisits. Merchant owner.

What it means: Chooses the date used for the validity window.

What exactly to enter or choose: Choose original paid/completed visit for a fixed window, or latest completed visit if that is your deliberate policy.

Why it matters / effect: The basis determines the date used for eligibility; latest-completed policies can extend eligibility as visits occur.

Options and starting value: Original paid visit / Latest completed visit Starting value: Original paid visit

How to save: Choose the dropdown and Save changes.

Common mistake: Choosing latest completed while promising customers a strictly fixed seven days from the first paid visit.

Check the result: Explain the same dated example to staff and compare with the eligibility quote.

Boundaries: Original paid service anchor and total free-visit count still apply. Plan/access dependency: Active merchant account.

S20. Require customer to be at location

Where / who: Merchant > Account > Settings > Location Verification. Merchant owner.

What it means: Restricts public QR requests to near the premises.

What exactly to enter or choose: Enable only if customers must be physically near your verified premises before public QR issuance.

Why it matters / effect: It requests customer location and checks distance, discouraging remote queue entry.

Options and starting value: On / Off Starting value: Off

How to save: Save exact Shop Profile coordinates first; switch on and Save changes.

Common mistake: Enabling before saving the correct business GPS, or assuming browser location permission is automatic.

Check the result: Test on a real phone at reception with location permission; provide staff assistance for permission failures.

Boundaries: Browser/device location permission and accuracy are required; this is not fraud-proof identity verification. Plan/access dependency: Active merchant account.

S21. Allowed distance

Where / who: Merchant > Account > Settings > Location Verification. Merchant owner.

What it means: Sets accepted distance around the exact shop coordinates.

What exactly to enter or choose: Choose a distance covering your actual reception area, for example 100 metres if that offered value fits your premises.

Why it matters / effect: A smaller radius is stricter but can reject genuine visitors when GPS is inaccurate indoors.

Options and starting value: 20-200 metres within app/server bounds. Starting value: 50 metres

How to save: Use distance controls and Save changes; test outdoors/at reception.

Common mistake: Entering 100 thinking it means kilometres, or increasing the radius to conceal a wrong map pin.

Check the result: Verify the unit shown and test near the edge; correct the business coordinates first.

Boundaries: GPS indoors can be inaccurate. Do not repeatedly change coordinates to a PIN centroid. Plan/access dependency: Active merchant account.

S22. Working days

Where / who: Merchant > Account > Settings > Business Hours. Merchant owner.

What it means: Identifies days the business operates.

What exactly to enter or choose: Select only the days on which you actually serve customers, for example Monday-Saturday.

Why it matters / effect: Public availability and business-time ETA should not assume Sunday service if the business is closed.

Options and starting value: Mon, Tue, Wed, Thu, Fri, Sat, Sun Starting value: All seven days

How to save: Toggle the day chips and Save changes.

Common mistake: Leaving every day selected because the initial defaults do.

Check the result: Open the saved schedule and check the next closed day as well as today's hours.

Boundaries: Closing a day is not a refund or automatic cleanup of existing tokens. Plan/access dependency: Active merchant account.

S23. Same timing and breaks for every working day

Where / who: Merchant > Account > Settings > Business Hours. Merchant owner.

What it means: Chooses common or individual schedules.

What exactly to enter or choose: Use common timing only when every selected day genuinely has the same hours and breaks; otherwise configure daily timing.

Why it matters / effect: It prevents accidental copying of weekday hours onto a short Saturday.

Options and starting value: On / Off Starting value: On

How to save: Set the checkbox, adjust common or daily cards, then Save changes.

Common mistake: Using common hours even though one day opens late or closes early.

Check the result: Reopen two different days and check both the opening interval and lunch break.

Boundaries: Check each day after switching mode; do not assume an overnight shift is supported. Plan/access dependency: Active merchant account.

S24. Opens / Closes

Where / who: Merchant > Account > Settings > Business Hours. Merchant owner.

What it means: Defines daily opening interval.

What exactly to enter or choose: Use the time pickers for real opening/closing, for example 09:00 to 18:00; opening must precede closing.

Why it matters / effect: ETA counts workable minutes and moves unfinished waiting time through closed periods to an available interval.

Options and starting value: Valid time pickers; opening before closing. Starting value: 09:00 / 21:00

How to save: Pick opening and closing times on the relevant card; Save changes.

Common mistake: Entering consultation duration here, or identical start/end to mean open for 24 hours.

Check the result: Check morning, closing-time and next-open-day examples; this is not a verified overnight-shift editor.

Boundaries: Do not enter the same opening and closing time to mean 24 hours. Plan/access dependency: Active merchant account.

S25. Breaks: Add / Start / End

Where / who: Merchant > Account > Settings > Business Hours. Merchant owner.

What it means: Removes scheduled break periods from available work time.

What exactly to enter or choose: Add a real non-serving interval, for example 13:00 to 14:00 for lunch, within valid daily hours.

Why it matters / effect: A longer wait crossing lunch includes the closed interval. A short wrap-up can use the schedule helper's limited spillover allowance; see the Smart ETA lesson.

Options and starting value: Valid non-overlapping break intervals inside the work period. Starting value: No breaks

How to save: Use Add in the break section, choose Start/End, then Save changes.

Common mistake: Adding a break for each customer's normal consultation or leaving an old lunch time active.

Check the result: With a sample wait across lunch, compare the expected turn time with the saved break and the documented spillover rule.

Boundaries: A current operational pause is a separate control; invalid/overlapping breaks may be rejected. Plan/access dependency: Active merchant account.

S26. Enable Advance Bookings

Where / who: Merchant > Account > Settings > Advance Booking (Appointments). Merchant owner.

What it means: Allows future slots for supported appointment workflows.

What exactly to enter or choose: Enable when you want entitled staff to create future appointments; complete the day/slot/notice settings too.

Why it matters / effect: An appointment reserves scheduled intent; it is separate from a waiting token until conversion/check-in.

Options and starting value: On / Off Starting value: Off

How to save: Switch on and Save changes; check Queue Dashboard Appointment.

Common mistake: Assuming turning it on creates public customer self-booking or guarantees service at an exact minute.

Check the result: Create an agreed sample appointment through the offered staff flow and verify its date/status.

Boundaries: A merchant route exists, but a direct active merchant navigation entry was not verified. Do not promise public QR self-booking. Plan/access dependency: Growth/Pro default capability.

S27. Max Advance Booking Days

Where / who: Merchant > Account > Settings > Advance Booking (Appointments). Merchant owner.

What it means: Limits how far ahead reception can book.

What exactly to enter or choose: Choose how far ahead staff may book, for example 7 days for the coming week.

Why it matters / effect: A smaller booking horizon reduces very distant commitments; it is unrelated to free-revisit validity.

Options and starting value: Current UI: 1, 2, 3, 7, 14, 30 days; backend range extends to 90. Starting value: 7

How to save: Choose a displayed value and Save changes.

Common mistake: Entering 7 here expecting to enable seven-day free revisits.

Check the result: Check the farthest selectable appointment date and configure revisits in their own section.

Boundaries: Use UI values; do not instruct customers to edit server configuration. Plan/access dependency: Advance bookings enabled and entitled.

S28. Slot Interval

Where / who: Merchant > Account > Settings > Advance Booking (Appointments). Merchant owner.

What it means: Sets spacing of appointment slots.

What exactly to enter or choose: Choose the spacing between offered start times, for example 15 minutes gives 10:00, 10:15 and 10:30.

Why it matters / effect: Slot spacing organises the appointment calendar. Service Avg time still estimates how long the actual work takes.

Options and starting value: Current UI: 15, 30, 45, 60 minutes. Starting value: 15 minutes

How to save: Choose the interval and Save changes.

Common mistake: Thinking a 15-minute slot guarantees every service takes 15 minutes or creates extra workers.

Check the result: Compare offered start times with service duration and the actual counter capacity.

Boundaries: Slot interval is not a guarantee of exact service duration. Plan/access dependency: Advance bookings enabled and entitled.

S29. Minimum Lead Time

Where / who: Merchant > Account > Settings > Advance Booking (Appointments). Merchant owner.

What it means: Requires notice before a bookable slot.

What exactly to enter or choose: Choose the notice needed before a slot, for example 30 minutes when staff need preparation time.

Why it matters / effect: At 10:00 with a 30-minute lead time, a 10:15 appointment is too close; other schedule/capacity rules also apply.

Options and starting value: Current UI: 0, 15, 30, 60, 120 minutes. Starting value: 30 minutes

How to save: Choose a value and Save changes.

Common mistake: Reading this as an arrival-lateness allowance or post-call no-show timeout.

Check the result: Try a too-near and a later slot in an agreed sample without creating unintended bookings.

Boundaries: Schedule, breaks and capacity still constrain dates. Plan/access dependency: Advance bookings enabled and entitled.

S30. Field label

Where / who: Merchant > Account > Settings > Token Form Fields > Custom token inputs > Manage > Add field / Edit field. Merchant owner.

What it means: Names the information you need.

What exactly to enter or choose: Enter a label the customer recognises, for example Vehicle number or Date of birth.

Why it matters / effect: This becomes the visible question; the label should make the requested answer unambiguous.

Options and starting value: 1-80 characters Starting value: Blank for new field

How to save: Use Add field or edit an existing field; configure this control, press Save field, then Save fields on the outer editor.

Common mistake: Using only Reference when customers cannot know which reference you mean.

Check the result: Open both staff and QR forms and ask a new user what answer they would enter.

Boundaries: Internal field key is stable when editing a saved label. Maximum 20 definitions per merchant; staff cannot edit definitions. Plan/access dependency: Active merchant account.

S31. Field type

Where / who: Merchant > Account > Settings > Token Form Fields > Custom token inputs > Manage > Add field / Edit field. Merchant owner.

What it means: Selects the input kind.

What exactly to enter or choose: Use Date for DOB, Text for vehicle/reference codes, Number for genuine quantities, or Dropdown for a fixed choice.

Why it matters / effect: The type controls input and validation. Identifiers may contain letters or leading zeros and usually belong in Text.

Options and starting value: Text / Number / Date / Dropdown / Yes / No Starting value: Text for new field

How to save: Use Add field or edit an existing field; configure this control, press Save field, then Save fields on the outer editor.

Common mistake: Using Number for AB00127, a vehicle registration or a reference with leading zeros.

Check the result: Enter a realistic sample including letters/leading zeros and verify the saved answer.

Boundaries: Changing meaning/type does not rewrite saved answers. Maximum 20 definitions per merchant; staff cannot edit definitions. Plan/access dependency: Active merchant account.

S32. Required

Where / who: Merchant > Account > Settings > Token Form Fields > Custom token inputs > Manage > Add field / Edit field. Merchant owner.

What it means: Makes an answer mandatory.

What exactly to enter or choose: Mark Required only when the visit cannot be handled without the answer; otherwise leave optional.

Why it matters / effect: Required means the form cannot proceed without a valid value on the enabled forms.

Options and starting value: On / Off Starting value: Off

How to save: Use Add field or edit an existing field; configure this control, press Save field, then Save fields on the outer editor.

Common mistake: Making an unnecessary sensitive detail compulsory or assuming required supplies a default answer.

Check the result: Try the form empty: required should block; optional should permit proceeding.

Boundaries: A required Yes/No answer may be No; it is still an answer. Maximum 20 definitions per merchant; staff cannot edit definitions. Plan/access dependency: Active merchant account.

S33. Active

Where / who: Merchant > Account > Settings > Token Form Fields > Custom token inputs > Manage > Add field / Edit field. Merchant owner.

What it means: Includes the field in future applicable forms.

What exactly to enter or choose: Keep Active on for a question still in use; turn it off to stop asking it on future forms.

Why it matters / effect: It controls future collection without rewriting old saved answers.

Options and starting value: On / Off Starting value: On

How to save: Use Add field or edit an existing field; configure this control, press Save field, then Save fields on the outer editor.

Common mistake: Turning it off and expecting historical answers to be erased.

Check the result: Open a fresh form, then separately inspect an existing sample token.

Boundaries: Inactive does not delete old answers. Maximum 20 definitions per merchant; staff cannot edit definitions. Plan/access dependency: Active merchant account.

S34. Show while generating token

Where / who: Merchant > Account > Settings > Token Form Fields > Custom token inputs > Manage > Add field / Edit field. Merchant owner.

What it means: Includes the field on token forms.

What exactly to enter or choose: Enable when staff and QR token creation should collect this field.

Why it matters / effect: The field must be in the token form's scope to appear during walk-in/QR issuance.

Options and starting value: Checked / Unchecked Starting value: Checked in new-field editor

How to save: Use Add field or edit an existing field; configure this control, press Save field, then Save fields on the outer editor.

Common mistake: Enabling appointment scope only and expecting the field in a walk-in form.

Check the result: Open a new Dashboard token form and the public QR details step.

Boundaries: At least one form scope must remain selected. Maximum 20 definitions per merchant; staff cannot edit definitions. Plan/access dependency: Active merchant account.

S35. Show while creating appointment

Where / who: Merchant > Account > Settings > Token Form Fields > Custom token inputs > Manage > Add field / Edit field. Merchant owner.

What it means: Includes the field on appointment forms.

What exactly to enter or choose: Enable when appointment creation should collect this answer as well.

Why it matters / effect: Appointment and token form scopes are separate; decide at which stage the information is needed.

Options and starting value: Checked / Unchecked Starting value: Checked in new-field editor

How to save: Use Add field or edit an existing field; configure this control, press Save field, then Save fields on the outer editor.

Common mistake: Assuming token scope automatically means appointment scope, or collecting the same sensitive answer unnecessarily.

Check the result: Open a new appointment form and check required/optional behaviour.

Boundaries: Required rules apply when the field is active in that scope. Maximum 20 definitions per merchant; staff cannot edit definitions. Plan/access dependency: Active merchant account.

S36. Dropdown options

Where / who: Merchant > Account > Settings > Token Form Fields > Custom token inputs > Manage > Add field / Edit field. Merchant owner.

What it means: Defines selectable answers.

What exactly to enter or choose: Enter the allowed choices clearly, for example Two-wheeler and Car for vehicle type.

Why it matters / effect: A fixed choice prevents inconsistent spellings and makes customer selection easier.

Options and starting value: 1-30 unique non-empty choices, each up to 80 characters Starting value: No options until entered

How to save: Use Add field or edit an existing field; configure this control, press Save field, then Save fields on the outer editor.

Common mistake: Creating a dropdown but leaving it without meaningful choices.

Check the result: Select every offered option in a sample form and check what is stored.

Boundaries: Required for Dropdown type; do not duplicate choices. Maximum 20 definitions per merchant; staff cannot edit definitions. Plan/access dependency: Active merchant account.

S37. Min characters / Max characters

Where / who: Merchant > Account > Settings > Token Form Fields > Custom token inputs > Manage > Add field / Edit field. Merchant owner.

What it means: Restricts Text length.

What exactly to enter or choose: Set sensible text lengths, for example a reference code's permitted minimum and maximum characters.

Why it matters / effect: Length checks reject obviously incomplete or excessively long entries; they cannot verify the real-world identity of a code.

Options and starting value: Optional min >=0; max 1-500; min <= max Starting value: No minimum; effective maximum 500

How to save: Use Add field or edit an existing field; configure this control, press Save field, then Save fields on the outer editor.

Common mistake: Setting the minimum so high that valid names/references fail.

Check the result: Try the shortest valid example, the longest valid example and one outside each boundary.

Boundaries: Only relevant to Text fields. Maximum 20 definitions per merchant; staff cannot edit definitions. Plan/access dependency: Active merchant account.

S38. Min value / Max value

Where / who: Merchant > Account > Settings > Token Form Fields > Custom token inputs > Manage > Add field / Edit field. Merchant owner.

What it means: Restricts numeric answers.

What exactly to enter or choose: Set the allowed numeric range for an actual quantity, for example 1-10 items.

Why it matters / effect: It rejects values outside the permitted quantity; it is not a text-code length limit.

Options and starting value: Finite optional numeric boundaries; minimum <= maximum Starting value: No explicit boundaries

How to save: Use Add field or edit an existing field; configure this control, press Save field, then Save fields on the outer editor.

Common mistake: Using a numeric range to validate a phone, vehicle registration or reference code.

Check the result: Test the minimum, maximum and one disallowed number.

Boundaries: Phone numbers and identifiers with leading zeroes are often better as Text. Maximum 20 definitions per merchant; staff cannot edit definitions. Plan/access dependency: Active merchant account.

S39. Min date / Max date

Where / who: Merchant > Account > Settings > Token Form Fields > Custom token inputs > Manage > Add field / Edit field. Merchant owner.

What it means: Restricts Date answers.

What exactly to enter or choose: Use real calendar limits if needed, for example a DOB cannot be later than the permitted maximum date.

Why it matters / effect: Calendar bounds restrict accepted dates; they do not calculate age or establish a medical eligibility policy by themselves.

Options and starting value: Valid YYYY-MM-DD dates; minimum <= maximum Starting value: No explicit boundaries

How to save: Use Add field or edit an existing field; configure this control, press Save field, then Save fields on the outer editor.

Common mistake: Entering today's date as a minimum when collecting dates of birth.

Check the result: Try a legitimate old birth date and a future date, and compare with the intended rules.

Boundaries: Use real calendar dates and the business date context. Maximum 20 definitions per merchant; staff cannot edit definitions. Plan/access dependency: Active merchant account.

S40. Allow past dates / Allow future dates

Where / who: Merchant > Account > Settings > Token Form Fields > Custom token inputs > Manage > Add field / Edit field. Merchant owner.

What it means: Allows dates before/after today.

What exactly to enter or choose: Allow past dates for DOB; allow future dates only for a question that needs them.

Why it matters / effect: These switches determine whether older/later dates are valid, alongside explicit date bounds.

Options and starting value: Independent On / Off switches Starting value: Both on

How to save: Use Add field or edit an existing field; configure this control, press Save field, then Save fields on the outer editor.

Common mistake: Disabling past dates on DOB, making almost every real customer unable to answer.

Check the result: Check yesterday, today and tomorrow in a sample form.

Boundaries: Can combine with date min/max; do not create an impossible range. Maximum 20 definitions per merchant; staff cannot edit definitions. Plan/access dependency: Active merchant account.

S41. Fields to show

Where / who: Merchant > Account > Display Devices > Display Settings. Merchant owner.

What it means: Selects optional customer details visible in the waiting room.

What exactly to enter or choose: Select only the public details visitors need, for example Name and Vehicle number; maximum two optional fields.

Why it matters / effect: Token/status remain core details. The selected optional fields can become Ranked columns; Counter appears only when there is a real assignment.

Options and starting value: Customer name and enabled custom fields; maximum 2 selected. Starting value: None

How to save: Tick only necessary fields and press Save changes.

Common mistake: Selecting a phone, DOB or private reference for public TV, or expecting unlimited optional columns.

Check the result: Use a sample with actual answers and inspect each layout; blank answers cannot appear magically.

Boundaries: Names and vehicle identifiers are personal details. Missing answers show no invented values. Plan/access dependency: Active merchant account.

S42. Layout

Where / who: Merchant > Account > Display Devices > Display Settings. Merchant owner.

What it means: Chooses the TV composition.

What exactly to enter or choose: Choose the offered layout after testing it on the actual TV; Ranked suits a table of token, selected details and status.

Why it matters / effect: Layout changes presentation, not queue order rules, token ownership or staff permissions.

Options and starting value: Default / Mercury / Classic / Ranked Queue / Counter Grid Starting value: Default

How to save: Choose a layout, save, then verify every paired screen.

Common mistake: Changing layout to fix an offline connection or missing source data.

Check the result: Check waiting, called, serving and completed examples at the physical viewing distance.

Boundaries: The Ranked option description in Merchant still mentions an older hero design; v24 uses a full-width table. Per-device layout selection not verified. Plan/access dependency: Active merchant account.

S43. Announce when

Where / who: Merchant > Account > Display Devices > Display Settings > Voice announcements. Merchant owner.

What it means: Chooses the event for spoken calls.

What exactly to enter or choose: Choose Called for next-turn announcements, Completed for collection, Both for both moments, or Off for silence.

Why it matters / effect: It determines which status transition produces a voice announcement; it does not change a token's status.

Options and starting value: Call Next (default) / Work completed / collection / Call Next and work completed / Announcements off Starting value: Call Next (called)

How to save: Choose the mode and Save changes.

Common mistake: Choosing Completed while expecting an announcement at Call Next.

Check the result: Call and complete a sample separately and confirm exactly which event speaks.

Boundaries: Requires unlocked TV audio and a supported voice/fallback; do not expect historical calls to replay. Plan/access dependency: Active merchant account.

S44. Spoken language

Where / who: Merchant > Account > Display Devices > Display Settings > Voice announcements. Merchant owner.

What it means: Chooses announcement language.

What exactly to enter or choose: Choose English, Hindi or both according to your waiting-room audience.

Why it matters / effect: It selects announcement language; actual speech still depends on supported device audio/voices and sound being enabled.

Options and starting value: English and Hindi / English / Hindi Starting value: English and Hindi

How to save: Choose the language, save and run sound check/sample call.

Common mistake: Expecting language selection to override a muted TV or autoplay restriction.

Check the result: Unlock audio and test the real TV in the chosen language.

Boundaries: A TV may lack a natural speech voice; recorded fallback is simpler. Plan/access dependency: Active merchant account.

S45. Collection message - English / Hindi

Where / who: Merchant > Account > Display Devices > Display Settings > Voice announcements. Merchant owner.

What it means: Customizes the work-completed collection instruction.

What exactly to enter or choose: Write a short collection instruction, for example Please collect your vehicle from reception, in each language you use.

Why it matters / effect: Completion announcements combine token identification with this collection wording; keep it appropriate to your business.

Options and starting value: Up to 240 characters per language; empty resolves to the standard message. Starting value: Your work is complete. Please collect your vehicle. (and the Hindi equivalent)

How to save: Select a completion mode, enter appropriate text and Save changes.

Common mistake: Using a vehicle message in a clinic, or including a private diagnosis/customer detail.

Check the result: Complete a sample and listen to the full token-plus-instruction announcement.

Boundaries: Recorded fallback cannot reproduce every custom sentence/name. This does not change WhatsApp templates. Plan/access dependency: Active merchant account.

S46. Haptic feedback

Where / who: Merchant > Account > Settings > App. Signed-in user on that device.

What it means: Controls local vibration feedback.

What exactly to enter or choose: Enable vibration feedback if useful on your supported phone; disable for a quieter interaction.

Why it matters / effect: It is device interaction feedback, not a customer alert, queue sound or server setting.

Options and starting value: On / Off Starting value: Enabled in local haptic service; device preference can differ.

How to save: Change the switch; test on a supported phone.

Common mistake: Assuming it makes a TV announce tokens.

Check the result: Try an ordinary supported action on that device and compare the preference.

Boundaries: No effect on token order, customer money or TV sound. Plan/access dependency: Active merchant account.

S47. Theme

Where / who: Merchant > Account > Settings > App. Signed-in user on that device.

What it means: Controls the app appearance.

What exactly to enter or choose: Choose the offered light/dark/system preference that is easiest to read on your device.

Why it matters / effect: It changes appearance; it does not change payment, priority or queue behaviour.

Options and starting value: System / Light / Dark Starting value: System in controller

How to save: Choose the offered dropdown option.

Common mistake: Expecting a theme choice to fix missing data or change the public TV layout.

Check the result: Read inputs, disabled actions and dialogs in the selected mode.

Boundaries: Theme persistence across installs/devices was not verified. Plan/access dependency: Active merchant account.

S48. InCue feedback form / My own link

Where / who: Merchant > Account > Customer Feedback > Feedback link on WhatsApp > Change. Merchant owner.

What it means: Chooses where a feedback button sends customers.

What exactly to enter or choose: Choose InCue feedback for ratings submitted in InCue, or My own link to send customers to your external review destination.

Why it matters / effect: The choice changes where the feedback request leads; external reviews are not automatically imported into InCue.

Options and starting value: InCue feedback form / My own link Starting value: InCue unless the account already has a custom destination

How to save: Choose the mode, enter a URL if needed and save through the offered action.

Common mistake: Expecting Google reviews to appear in InCue's internal feedback report.

Check the result: Open an eligible sample feedback link and check the destination before rollout.

Boundaries: External ratings stay external and are not imported into InCue. Plan/access dependency: Feedback entitlement / account configuration.

S49. Your feedback link

Where / who: Merchant > Account > Customer Feedback > Feedback link on WhatsApp > Change. Merchant owner.

What it means: Sets an external review destination.

What exactly to enter or choose: Paste the complete HTTPS review URL for this business, then open it yourself.

Why it matters / effect: A valid destination prevents customers landing on a wrong business or a broken page.

Options and starting value: Valid allowed web URL; HTTPS recommended/normalized by the editor Starting value: Empty until provided

How to save: Select My own link, enter the official review URL, save and test it.

Common mistake: Pasting an admin-only link, an OTP/session URL or another outlet's review link.

Check the result: Open from a signed-out phone and verify the business and review page.

Boundaries: Do not paste a private customer token or gateway link. Plan/access dependency: Custom feedback mode and account configuration.

S50. Legal business name

Where / who: Merchant > Account > Subscription & Billing > Plans, marketplace & billing details > Billing & GST details. Merchant owner.

What it means: Provides invoice recipient details.

What exactly to enter or choose: Enter the legal recipient name used by your business for InCue billing.

Why it matters / effect: The subscription/add-on invoice should identify the correct purchaser, which can differ from the shop's short public name.

Options and starting value: Legal entity text Starting value: Account-specific; not a universal default.

How to save: Open Billing details, change this field and Save; review the next quote/invoice.

Common mistake: Using a customer's name or assuming an old issued invoice will be rewritten.

Check the result: Review the checkout recipient before payment and the issued invoice afterward.

Boundaries: Changing a profile is not a promise to rewrite an already issued invoice. Contact support for correction. Plan/access dependency: Active merchant account.

S51. GSTIN (optional for unregistered business)

Where / who: Merchant > Account > Subscription & Billing > Plans, marketplace & billing details > Billing & GST details. Merchant owner.

What it means: Provides invoice recipient details.

What exactly to enter or choose: Enter your business GSTIN exactly if registered; leave optional when unregistered.

Why it matters / effect: Correct billing tax identity matters for the invoice; GSTIN alone does not promise eligibility for any tax credit.

Options and starting value: Valid GSTIN where applicable Starting value: Account-specific; not a universal default.

How to save: Open Billing details, change this field and Save; review the next quote/invoice.

Common mistake: Entering a made-up/sample GSTIN or relying only on the Shop Profile GST field.

Check the result: Compare with your registration document and verify the checkout billing details.

Boundaries: Changing a profile is not a promise to rewrite an already issued invoice. Contact support for correction. Plan/access dependency: Active merchant account.

S52. Street / billing address

Where / who: Merchant > Account > Subscription & Billing > Plans, marketplace & billing details > Billing & GST details. Merchant owner.

What it means: Provides invoice recipient details.

What exactly to enter or choose: Enter the actual billing address associated with the purchaser.

Why it matters / effect: It forms part of billing identity and should agree with your records.

Options and starting value: Address text Starting value: Account-specific; not a universal default.

How to save: Open Billing details, change this field and Save; review the next quote/invoice.

Common mistake: Copying the visiting customer's address or leaving a former premises address.

Check the result: Check the full billing summary before confirming a purchase.

Boundaries: Changing a profile is not a promise to rewrite an already issued invoice. Contact support for correction. Plan/access dependency: Active merchant account.

S53. City

Where / who: Merchant > Account > Subscription & Billing > Plans, marketplace & billing details > Billing & GST details. Merchant owner.

What it means: Provides invoice recipient details.

What exactly to enter or choose: Enter the city for that billing address, for example Ambala.

Why it matters / effect: Billing location should be consistent with the address, state and PIN.

Options and starting value: Billing city text Starting value: Account-specific; not a universal default.

How to save: Open Billing details, change this field and Save; review the next quote/invoice.

Common mistake: Entering the service customer's city instead of the purchaser's.

Check the result: Read the complete billing address together before paying.

Boundaries: Changing a profile is not a promise to rewrite an already issued invoice. Contact support for correction. Plan/access dependency: Active merchant account.

S54. State (full name)

Where / who: Merchant > Account > Subscription & Billing > Plans, marketplace & billing details > Billing & GST details. Merchant owner.

What it means: Provides invoice recipient details.

What exactly to enter or choose: Enter/select the full correct state name, for example Haryana, as accepted by the form.

Why it matters / effect: Billing state is used in location/tax handling; a typo can cause incorrect or rejected details.

Options and starting value: Recognized full state name Starting value: Account-specific; not a universal default.

How to save: Open Billing details, change this field and Save; review the next quote/invoice.

Common mistake: Typing a city here or using an unrecognised shorthand.

Check the result: Compare state with GST registration where applicable and inspect the final tax breakdown.

Boundaries: Changing a profile is not a promise to rewrite an already issued invoice. Contact support for correction. Plan/access dependency: Active merchant account.

S55. PIN code

Where / who: Merchant > Account > Subscription & Billing > Plans, marketplace & billing details > Billing & GST details. Merchant owner.

What it means: Provides invoice recipient details.

What exactly to enter or choose: Enter the six-digit PIN for the billing address.

Why it matters / effect: It completes the purchaser's postal address; it is separate from customer or QR GPS details.

Options and starting value: Valid postal code Starting value: Account-specific; not a universal default.

How to save: Open Billing details, change this field and Save; review the next quote/invoice.

Common mistake: Using a convenient PIN from a different city.

Check the result: Verify city, state and PIN agree before issuing the purchase invoice.

Boundaries: Changing a profile is not a promise to rewrite an already issued invoice. Contact support for correction. Plan/access dependency: Active merchant account.

S56. Billing email

Where / who: Merchant > Account > Subscription & Billing > Plans, marketplace & billing details > Billing & GST details. Merchant owner.

What it means: Provides invoice recipient details.

What exactly to enter or choose: Enter a monitored business billing email, for example accounts at your own business domain.

Why it matters / effect: It records the contact for billing communication; it does not replace the registered mobile login.

Options and starting value: Valid email address Starting value: Account-specific; not a universal default.

How to save: Open Billing details, change this field and Save; review the next quote/invoice.

Common mistake: Entering an unmonitored staff email or assuming it changes OTP delivery.

Check the result: Check spelling, save and reopen; use offered invoice/receipt tools as well.

Boundaries: Changing a profile is not a promise to rewrite an already issued invoice. Contact support for correction. Plan/access dependency: Active merchant account.

S57. Base plan

Where / who: Merchant > Account > Subscription & Billing > Plans, marketplace & billing details. Merchant owner.

What it means: Selects the required subscription tier.

What exactly to enter or choose: Choose the plan whose real staff/display/feature limits fit your operation.

Why it matters / effect: The mandatory base plan grants the core entitlements; optional extras sit above it.

Options and starting value: Plans currently offered by the catalog Starting value: Current account selection

How to save: Change the selection, Review price & service dates, approve the listed items/total, then complete payment.

Common mistake: Choosing solely by the price without checking seats, dates and renewal terms.

Check the result: Review the current quote, active dates and entitlements after successful payment.

Boundaries: A base plan is required; add-ons alone do not replace it. Plan/access dependency: Catalog/account eligibility and base plan.

S58. Monthly / Yearly

Where / who: Merchant > Account > Subscription & Billing > Plans, marketplace & billing details. Merchant owner.

What it means: Selects subscription period.

What exactly to enter or choose: Choose Monthly or Yearly based on the period you actually want to purchase.

Why it matters / effect: It changes the billed service period and total quote; a yearly total is not the monthly price multiplied by an assumed offer.

Options and starting value: Monthly / Yearly Starting value: Current account period

How to save: Change the selection, Review price & service dates, approve the listed items/total, then complete payment.

Common mistake: Reading a yearly amount as a one-month amount or ignoring GST in checkout.

Check the result: Read the service dates and tax-inclusive payable total before paying.

Boundaries: Check service dates and the actual total, not only monthly equivalent. Plan/access dependency: Catalog/account eligibility and base plan.

S59. Upgrade for the remaining period

Where / who: Merchant > Account > Subscription & Billing > Plans, marketplace & billing details. Merchant owner.

What it means: Chooses immediate prorated upgrade where eligible.

What exactly to enter or choose: Use the remaining-period upgrade only when you intend to change the current plan mid-term.

Why it matters / effect: The quote calculates the applicable remaining-period change; it is different from purchasing an entirely new full period.

Options and starting value: On / Off where offered Starting value: Off unless selected

How to save: Change the selection, Review price & service dates, approve the listed items/total, then complete payment.

Common mistake: Assuming a plan tap already activates an upgrade or that every change is automatically refunded.

Check the result: Approve only the displayed quote, then verify updated entitlement and service dates.

Boundaries: Downgrades apply at renewal; server eligibility applies. Plan/access dependency: Catalog/account eligibility and base plan.

S60. Optional services / quantity

Where / who: Merchant > Account > Subscription & Billing > Plans, marketplace & billing details. Merchant owner.

What it means: Chooses optional extras.

What exactly to enter or choose: Select the optional service you need and the real quantity, such as one additional entitled display where offered.

Why it matters / effect: Extras have their own scope, dates, tax and price; some features may already be included or temporarily bundled.

Options and starting value: Available catalog items and allowed quantities Starting value: Current active/scheduled quantities

How to save: Change the selection, Review price & service dates, approve the listed items/total, then complete payment.

Common mistake: Buying an extra twice, assuming every advertised future add-on is self-service, or ignoring existing included limits.

Check the result: Compare active extras with the plan and final line-item quote; contact support if checkout is unavailable.

Boundaries: Do not reduce below active usage. Current checkout/support availability varies. Plan/access dependency: Catalog/account eligibility and base plan.

S61. Phone number / Name

Where / who: Merchant > Staff > Add Staff / edit member. Merchant owner.

What it means: Identifies the staff login and person.

What exactly to enter or choose: Use the staff member's own authorised mobile and recognisable name.

Why it matters / effect: Their mobile/OTP identifies their login; a separate name does not create a second independent login on the owner's phone.

Options and starting value: Valid 10-digit mobile and non-empty name Starting value: Empty for a new staff member

How to save: Configure the staff form, save and verify the staff card/login.

Common mistake: Giving several people the owner's number or sharing OTPs.

Check the result: Have that staff member sign in and confirm the correct business/access badge.

Boundaries: Phone ownership and one active session matter; no password-reset setting. Plan/access dependency: Available staff seat and active account.

S62. Dashboard user / Counter user

Where / who: Merchant > Staff > Add Staff / edit member. Merchant owner.

What it means: Selects work access mode.

What exactly to enter or choose: Choose Dashboard user for reception work; Counter user for a worker serving assigned services.

Why it matters / effect: Access mode controls available operations and scope; it is not merely a different visual theme.

Options and starting value: Dashboard user / Counter user; Staff app user is future-disabled in this editor Starting value: Dashboard in current add form

How to save: Configure the staff form, save and verify the staff card/login.

Common mistake: Giving broad reception access to someone who should handle one counter only.

Check the result: Use that person's own login and inspect the allowed actions and visible queue.

Boundaries: Counter requires at least one service; Staff app deployment is not promised. Plan/access dependency: Available staff seat and active account.

S63. Reports access / Customer history

Where / who: Merchant > Staff > Add Staff / edit member. Merchant owner.

What it means: Grants extra Dashboard visibility.

What exactly to enter or choose: Grant reports/history only to staff who need the relevant customer/business records.

Why it matters / effect: Permissions restrict sensitive visibility separately from basic queue operation; date scope depends on the offered interface/account.

Options and starting value: Independent permissions; Manage queue is fixed on for Dashboard Starting value: Extra permissions off unless selected

How to save: Configure the staff form, save and verify the staff card/login.

Common mistake: Turning everything on for convenience or assuming all report date ranges are identical across versions.

Check the result: Check both an allowed view and a view that should remain unavailable.

Boundaries: The screen limits offered report dates; no owner settings/billing access is granted. Plan/access dependency: Available staff seat and active account.

S64. Counter name

Where / who: Merchant > Staff > Add Staff / edit member. Merchant owner.

What it means: Names the work point for Counter access.

What exactly to enter or choose: Use a real public-facing desk/room label, for example Room 2 or Service Bay 1.

Why it matters / effect: It helps the called visitor find the assigned place and can appear on TV when there is an assignment.

Options and starting value: Text; form can fall back to staff name Starting value: Staff name/default form fallback

How to save: Configure the staff form, save and verify the staff card/login.

Common mistake: Inventing counters when the business has none or putting a private staff phone in the name.

Check the result: Call an assigned sample and check the destination on Dashboard and TV.

Boundaries: A counter label alone does not create serving capacity, an assigned worker or a separate TV display. Plan/access dependency: Available staff seat and active account.

S65. Services

Where / who: Merchant > Staff > Add Staff / edit member. Merchant owner.

What it means: Restricts Counter work to compatible catalog services.

What exactly to enter or choose: Assign only services this Counter user can actually perform, for example Consultation but not Lab collection.

Why it matters / effect: Compatibility affects assignment and ETA capacity. A multi-service token needs a counter covering its full selected set in service-aware routing.

Options and starting value: One or more selected active services Starting value: None until selected

How to save: Configure the staff form, save and verify the staff card/login.

Common mistake: Selecting all services merely to make auto assignment work.

Check the result: Try one compatible service and one incompatible combination with an agreed sample.

Boundaries: An unassigned service cannot be handled by assuming a generic role. Plan/access dependency: Available staff seat and active account.

S66. Ad name

Where / who: Merchant > Account > Ads on TV > upload / creative menu. Merchant owner.

What it means: Names media in your creative list and reports.

What exactly to enter or choose: Enter a recognisable internal creative name, for example October service reminder.

Why it matters / effect: It helps the owner distinguish uploaded ads in the library/report; the media itself carries the public message.

Options and starting value: Non-empty text accepted by upload/rename form Starting value: Empty/new suggested form value

How to save: Set the upload/menu option and wait for acknowledgement; check the TV.

Common mistake: Using the filename as the only clue when many similar versions exist.

Check the result: Check the right thumbnail, media and name before publishing.

Boundaries: Not a customer-targeting rule or guarantee of reach. Plan/access dependency: Active Ads on TV add-on and display entitlement.

S67. Show on TV for

Where / who: Merchant > Account > Ads on TV > upload / creative menu. Merchant owner.

What it means: Sets image display time.

What exactly to enter or choose: For an image, choose a readable on-screen dwell such as 10 seconds, within the offered limits.

Why it matters / effect: This controls how long a slide stays visible in rotation; it is unrelated to service duration or appointment slots.

Options and starting value: Minimum 3 seconds; maximum current ad-duration limit Starting value: 10 seconds for images

How to save: Set the upload/menu option and wait for acknowledgement; check the TV.

Common mistake: Using three seconds for a dense slide that visitors cannot read.

Check the result: Read the whole slide from the waiting seats before deciding its dwell time.

Boundaries: Video time is measured from the file, not this image setting. Plan/access dependency: Active Ads on TV add-on and display entitlement.

S68. Creative active / paused

Where / who: Merchant > Account > Ads on TV > upload / creative menu. Merchant owner.

What it means: Chooses whether uploaded media participates in playback.

What exactly to enter or choose: Keep Active for a creative you intend to rotate; pause an outdated/incorrect creative.

Why it matters / effect: Only eligible active media in an entitled working ad setup can play; pause stops that creative's intended rotation.

Options and starting value: Activate / Pause through offered item actions Starting value: Publish on upload if capacity permits; otherwise paused

How to save: Set the upload/menu option and wait for acknowledgement; check the TV.

Common mistake: Expecting Active to fix an expired add-on, unsupported codec or disconnected TV.

Check the result: Watch a full rotation on the real TV and check entitlement/format separately if absent.

Boundaries: Default 5 active and 10 stored; account overrides and add-on expiry apply. Plan/access dependency: Active Ads on TV add-on and display entitlement.

S69. Payment gateway provider

Where / who: Merchant > Account > Online Payments. Merchant owner.

What it means: Selects a supported merchant-owned payment connection.

What exactly to enter or choose: Select the supported provider for your business's approved payment account.

Why it matters / effect: QR payment collection depends on the matching provider configuration, approval and credentials.

Options and starting value: Only enabled provider cards; others may say Coming soon Starting value: No verified universal connected gateway

How to save: Open the supported connection form, enter your own correct credentials, Connect & verify and check its status.

Common mistake: Selecting a provider before the business account is approved or assuming a connection test proves settlement.

Check the result: Follow your approved provider setup and verify the offered status; use an authorised live payment acceptance check separately.

Boundaries: Do not share keys; removing the connection changes checkout behaviour but does not refund old orders. Provider availability/approval and account configuration apply. Plan/access dependency: Supported provider and approved account.

S70. Gateway key / secret fields

Where / who: Merchant > Account > Online Payments. Merchant owner.

What it means: Connects your approved payment account.

What exactly to enter or choose: Paste the matching keys/secrets issued by your own selected provider into their exact fields; obtain them from its secure portal.

Why it matters / effect: The backend needs correct credentials to use that merchant account. These are secrets, not customer-facing text.

Options and starting value: Provider-specific credentials, masked where displayed Starting value: Not connected until verified

How to save: Open the supported connection form, enter your own correct credentials, Connect & verify and check its status.

Common mistake: Pasting test keys into a live setup, another business's keys or sending secrets in support screenshots.

Check the result: Use the offered secure test/status, mask all secrets and separately verify the approved live payment flow.

Boundaries: Do not share keys; removing the connection changes checkout behaviour but does not refund old orders. Secrets are confidential; test credentials do not establish live payment receipt. Plan/access dependency: Supported provider and approved account.

S71. Link Google Account / Unlink Google Account

Where / who: Merchant > Account > Linked Accounts. Merchant owner.

What it means: Adds or removes the offered linked Google sign-in path for this merchant identity.

What exactly to enter or choose: Link only the Google identity authorised for this owner account using the offered verification flow.

Why it matters / effect: It provides an additional supported sign-in route; it does not create a staff permission or change the registered phone by itself.

Options and starting value: Link Google Account or Unlink Google Account, according to current linked state. Starting value: Account-specific; the screen reports its current linked email/state.

How to save: Open Linked Accounts, choose the appropriate action and complete the provider confirmation. Verify the resulting linked state before relying on Google sign-in.

Common mistake: Linking a shared/public computer identity or assuming unlinking deletes merchant data.

Check the result: Verify which Google account is linked and keep access to the registered mobile before unlinking.

Boundaries: Requires the correct Google identity and provider/platform support. This does not replace phone ownership or grant staff owner access. Account-recovery execution was not tested. Plan/access dependency: Authenticated merchant account and available provider flow.