Your VIDIK360 field guide

Choose the measurement you need

• Maps / GEO: where does a business appear in Google Maps results for a keyword checked from specific coordinates?
• Organic search / SEO: where does an owned website appear among Google's organic results for a query, market and device? A Search local-pack result is a separate measurement, not an organic position or a Maps-grid check.
• AI visibility / AEO: does a supported AI answer mention a business or use a source that cites its website? A mention, citation and reviewed recommendation are different findings.
• Choose only the modules you need now. You can save incomplete setup and return later. There is no combined score that proves revenue, leads or total market share.

The first-run sequence

1. Check the current workspace and project. Choose One business or Multiple businesses, then select the modules you want to configure.
2. Add the businesses you own or are authorized to track. Attach each website to the appropriate business when configuring organic search. Maps-only setup does not require a website.
3. Add enabled Maps keywords, organic queries or AI questions in their own module. Use Add one, Paste multiple or Import CSV; review the destination and duplicates.
4. Choose Coverage: Maps coordinates, Search locations/devices or supported AI market contexts. These are separate inputs; an AI question does not use every point on a Maps grid.
5. Review and save the draft. Check the saved business, keyword and enabled-location counts. Added to draft is not the same as Saved; Saved is not a guarantee of live authorization.
6. Open the module's Run scan review. Confirm the full or explicitly smaller scope, mode, observations, current server quote, balance and access status. Submit once only when the review says the selected scope is permitted.

A small practice setup

Fictitious example, not a recommended search-volume strategy: SAMPLE Maple Path Plumbing, one keyword such as emergency plumber, and a reviewed 5 × 5 point grid. With 25 enabled points, one keyword and Standard mode, the ordinary Maps example is 25 credits. Turning five points off leaves 20 checks and 20 credits. The application quote is authoritative.

Replace every SAMPLE name and example domain with your own verified information. Do not enter a made-up Place ID or map centre to get past a required field. Inspect the first result's evidence before expanding the scope.

What belongs in each field

• Workspace: the authorized working area shared with your team. Project: the collection of businesses and tracking settings you are managing. Check both before saving or importing.
• Business name: the real company or public listing name, such as SAMPLE Maple Path Plumbing. A service category such as plumber belongs in Keywords, not in this field as a substitute for the business identity.
• Website/domain: the owned website attached to that business. Full URLs can be normalized to a hostname by the importer. sample.example is an illustrative placeholder, not a real website. A path on a website is not a separate business by itself.
• Google Place ID: a verified public listing identifier, if known. Leave it blank in a draft if unknown. A Google Business Profile account/location resource identifier is not interchangeable with a public Place ID.
• Aliases: reviewed real names used by the same business. Do not add broad category words or a competitor's name to force a match. Distinct branches can share a name or domain and should remain distinct.
• Address and business coordinates: verified business information only. Keep hidden service-area addresses private. Service-area-only import removes precise address/coordinates rather than exposing a private location.

What counts as an owned result

Confirmed stable listing identifiers take priority. Exact-name fallback normalizes case and repeated whitespace; a collision needs review. A similar name is not enough to claim ownership. Organic matching follows exact owned hostname/subdomain rules, not lookalike text in an unrelated domain.

All my brands uses the businesses tracked in the selected scan. Selecting one brand changes your displayed scope; it does not make your other known brands external competitors. Multiple owned businesses matched within one fetched observation do not multiply credits.

Blank domains and Place IDs can remain saved drafts. Before scanning, enable a named business and the module's required inputs. Organic search needs an owned domain on an enabled business. Review name ambiguity and missing identity evidence rather than treating unmatched results as proof of misconfiguration.

Business, website, workspace and team limits are separate from credits. The current account's entitlements and any owner-approved tester allowances govern saves/imports. More credits do not automatically raise those limits.

Choose useful keywords

Use ordinary searches describing services you actually provide. Fictitious plumbing examples: plumber, emergency plumber, drain cleaning, water heater repair. These are brainstorming examples, not measured search volume or proven opportunities. Put one query on each line when pasting; do not paste a paragraph of instructions into a keyword field.

A city in the keyword is literal query text, while the map point is the search origin. plumber and plumber Toronto ask different questions. A branded query can test a business name but answers a different question from a non-branded category search. Keep these groups understandable when comparing results.

The ordinary Maps/Search rate card does not accept search operators such as site:, inurl: or intitle:, quoted search syntax, multiline queries or backslashes. Do not add paid extras or unsupported syntax to a normal keyword.

Generate, import or edit points

1. Open Coverage and choose Generate a grid, Import coordinates or Add a point manually. Use verified business coordinates as a starting centre when available; otherwise choose and review the centre yourself.
2. Start with the 5 × 5 preset when appropriate. Grid rows × columns determine point count. Geographic width × height describe the area; a 5 km × 5 km area is not a 5 km radius and does not itself multiply credits.
3. Review spacing/area units. In edit mode, click or tap points to include/exclude them. Disabled points remain visible. Use Enable all, Disable all, Reset selection or Undo as needed. Panning should not toggle points.
4. Keep at most 250 enabled Maps points. Existing saved-point and import bounds still apply. Check total versus enabled counts; the quote uses the selected enabled scope.
5. When changing existing geometry or importing coordinates, explicitly choose Append or Replace. Review the preview before applying it to the draft; then save the project. Cancel leaves the saved setup unchanged. Reload to confirm exclusions persisted.
6. Use results mode to inspect evidence; use setup edit mode to alter future points. Editing future coverage does not change a historical scan's coordinates. A larger area may make old/new runs only partly comparable.

Reading the map

Illustrative Standard example: 25 enabled points × 10 keywords = 250 credits per run. Four runs use 1,000 credits. The same returned results can be checked against multiple owned brands without multiplying those credits. Area dimensions do not add a separate credit multiplier.

A single-keyword map shows the best owned rank for each eligible point, with distinct greens for positions 1, 2 and 3 and numeric labels. An all-keywords map shows coverage with its own denominator; that percentage is not one ranking position. Use the legend and accessible result list.

No match within the verified checked depth is different from failed, pending, missing or not planned. Never interpret an unloaded tile, blank region or absent marker as a zero rank. The basemap supplies geography; saved result evidence supplies rankings. Loading maps, selecting points and changing styles do not start scans or spend VIDIK360 credits.

Fill in the Search fields

• Owned website: add the actual domain to the appropriate enabled business. You do not need a different query for every owned brand; one returned result can be matched against all eligible owned domains.
• Query: an ordinary customer search, for example drain cleaning Toronto. Each enabled query is checked at each selected Search location and device. Keyword presence on your website is not a rank measurement.
• Location label: your readable name, such as Toronto. Provider location: the supported full market name, for example Toronto,Ontario,Canada. A nickname or a bare unverified city is not guaranteed to be accepted.
• Language: a supported language code, such as en. Device: desktop, mobile or both where offered. Desktop and mobile create separate observations. Device/depth settings are project options, not extra CSV columns to invent.
• Depth: the supported ordinary Search settings are 10 or 20 organic results. The ordinary Standard observation costs 2 credits in either case; absence of your website does not reduce the charge. Unsupported deeper/enriched requests must be blocked or separately quoted.

Read positions and evidence correctly

Organic position uses the organic result group, excluding ads and local-pack positions. Open a row to inspect the matching domain/URL and timestamp. Not found in the top N is meaningful only when retrieval evidence supports that depth; missing retrieval is unknown.

Illustrative Standard example: 10 queries × 1 supported location × 1 device × 2 credits = 20 credits per run. Four runs use 80 credits. Two devices double those observations. This is an example from one shared wallet, not a separate SEO allowance.

Write a prompt for the answer you want to observe

Use the question a prospective customer might ask, not an instruction telling the model to promote you. Fictitious examples: Which plumbers offer emergency service in Toronto? What should I compare when choosing a drain-cleaning company in Toronto? These are sample ideas, not evidence of demand or likely answers.

An unbranded question tests discovery. What do you know about SAMPLE Maple Path Plumbing? tests a branded question. Keep those purposes separate; explicitly mentioning your brand in the question is not proof of spontaneous recommendation. Never add private customer information or credentials to prompts.

Choose supported contexts, not GPS points

• ChatGPT LLM Scraper uses supported country/region markets, for example Canada. Toronto is not a supported ChatGPT market in the verified catalog. Put Toronto explicitly in the question when that is what you want to ask; this does not turn the request into a precise Toronto GPS observation.
• Gemini LLM Scraper supports reviewed city markets such as Toronto,Ontario,Canada. For a city context, explicitly choose Gemini only. For a shared ChatGPT/Gemini setup, choose a supported market common to both, such as Canada, and put any intended city in the prompt.
• Changing a location or platform is an explicit draft edit followed by Save. The application must not silently convert Toronto to Canada or drop a selected platform. Check the collection-availability labels and resulting quote.
• Platforms and response samples multiply observations. Two platforms × three samples = six answers per prompt/context. Repeated samples are intentional separate observations, not retry duplicates. The offered sample limit and current account limits remain authoritative.
• Google AI Overviews and Google AI Mode are different Google search surfaces. They are not ordinary Gemini responses. Treat them as draft-only unless the live availability check explicitly permits them under an approved policy. Each Google surface requires its own separate quote; do not mix it with ChatGPT/Gemini or another Google surface in one run.

What an AI result can establish

Mentioned means answer text mentions the entity; Cited means a used source supports the recorded citation evidence. Recommendation is a separate reviewed assessment; unreviewed stays unreviewed. A citation without a name mention and a mention without a citation are possible. There is no ordinal AI rank.

Open answer evidence for excerpts, citations, platform context and timestamp. One answer is a sample, not stable visibility for all users. Keep platforms separate and show sample counts. A successfully checked Google SERP with no AI Overview is different from a failed or uncollected request, when that surface is available.

Illustrative Standard example: 5 prompts × 2 supported platforms × 1 common market × 3 samples × 3 credits = 90 credits per run. Four runs use 360 credits. This rate is for the supported ChatGPT/Gemini scraper paths, not token-priced model calls, arbitrary AI engines or AI-written reports.

Choose the simplest input method

• Use Add one for a single item. Use Paste multiple for lines or spreadsheet columns in the appropriate business, website, term or context editor. Websites need an explicit business association. Use Import CSV for structured rows and download that dialog's example.
• The general importer accepts one type per batch: businesses, Maps points, Maps keywords, SEO queries, SEO locations, AEO prompts or AEO contexts. It does not create one paid project per row. The preview names the workspace/project destination.
• CSV requires headers, UTF-8 and comma-separated cells. Quote cells containing commas; double embedded quotes. The general importer is bounded at 500 data rows, 64 columns and 1 MiB of file/request data, with 4,000 characters per cell. Split oversized files rather than assuming truncation.
• For Maps keywords, SEO queries or AEO prompts use text,enabled, with keyword/query/prompt aliases recognized. Locations use label,locationName,languageCode,enabled. A supported full location containing commas must be quoted in CSV.
• Business columns can include name,domains,placeIds,aliases,address,serviceArea,serviceAreaOnly,lat,lng,enabled. Semicolon or | separates multiple domains/IDs/aliases. A supplied id must be an existing VIDIK360 item ID in this project's collection; do not paste a Google resource ID there.

Coordinate template

The second line is a template with placeholders, not an import-ready coordinate or a claimed location. Replace both coordinate placeholders with reviewed numeric latitude/longitude. Latitude comes first. Common aliases include point/name, latitude and longitude.

Explicit enabled=false (also no or 0) must stay disabled. The coordinate preview explains its default when enabled is absent. The general importer defaults to disabled drafts; its explicit Include valid imported rows in tracking after review choice enables valid new rows while retaining explicit exclusions. Review the final enabled count before applying.

label,area,lat,lng,enabled
SAMPLE point,SAMPLE area,<verified latitude>,<verified longitude>,true

Resolve identities and commit safely

1. Review auto-mapped headers, errors and duplicates. Correct unmapped columns. Download the error output where offered; do not suppress invalid coordinates or unclear business associations.
2. Choose Create, Match existing, Update selected fields or Skip. Shared domains do not merge branches. Ambiguous same-name businesses require review. Update only the fields you intend to change.
3. Check enabled status and Append versus Replace for coordinates. A preview is not a saved project. The inline onboarding path adds to the current draft until final Save; the separate durable import dialog explicitly applies its reviewed batch.
4. Keep the same import batch when retrying an interrupted apply. Version/entitlement conflicts are rechecked at commit; refresh/review the saved state instead of repeatedly creating new batches. Importing never starts a scan or schedule.

Templates and migration limits

Templates reuse reviewed terms, module/settings choices and relative grid setup. Preview expanded city/service placeholders and the new location anchor. They do not copy client identities, observations, credentials, report links, credits or history. A schedule reminder is not an enabled schedule or budget.

Current CSV migration imports configuration, not another vendor's ranking history. Do not rename arbitrary vendor export columns and assume historical metric equivalence. GBP connection/import requires its own configured access and approval; a draft or sample interface is not proof of a live Google connection.

Ordinary observation rates

Maps unit: one keyword at one coordinate and supported search configuration, requesting up to 100 listings. Search unit: one keyword/location/device/language configuration, requesting up to 20 organic results. AI unit: one prompt/supported ChatGPT or Gemini platform/context/sample.

Priority is 2× and Live is 4× ordinary Standard credits; availability depends on the current policy. Processing is asynchronous for queued modes. A speed label is not a guaranteed completion time. Provider-paid extras and unsupported configurations are not implicitly included.

Read the server-generated quote's mode, observations, price version, credit charge and remaining balance. It is authoritative; this guide and your LLM's arithmetic are illustrations. Exact duplicate observations within an authorized run may deduplicate; intentional AI samples remain separate. Additional owned-brand or competitor matches are free.

• Maps: Standard 1, Priority 2, Live 4 credits per eligible observation.
• Organic search: Standard 2, Priority 4, Live 8 credits per eligible observation.
• ChatGPT / Gemini: Standard 3, Priority 6, Live 12 credits per eligible observation.

Approved plans, actual account terms

Annual offers save 20% against twelve monthly payments and issue credits monthly, not all at once. Prices are before applicable tax. All three modules share the same wallet; usage examples are not three independent allowances. Billing and the server catalog show your actual offer; legacy contracts, tester grants and owner overrides may differ.

Under the approved subscription policy each monthly grant lasts its own service month plus the following one: a January 17 grant expires March 17. Eligible lots spend in earliest-expiry order. Top-ups require active paid access to purchase/use, expire 12 calendar months after payment, and are not automatically purchased. Legacy lots retain their original terms. Tester/promotional grants have their own displayed expiry/access rules; do not assume the top-up subscription rule applies to an authorized tester grant.

Available, reserved, consumed and expired credits are different states. A run reserves before submission; valid no-match observations still count as successful checks. Definitively unused reservations can be released. Unknown provider outcomes may remain reserved for reconciliation; do not treat them as a confirmed zero cost or submit replacements blindly.

• Starter: $19.00 USD/month and 7,000 monthly credits; $182.40 USD upfront annually.
• Growth: $49.00 USD/month and 18,000 monthly credits; $470.40 USD upfront annually.
• Pro: $88.00 USD/month and 35,000 monthly credits; $844.80 USD upfront annually.

Billing, referrals and account controls

Billing shows your actual subscription, eligible credit lots and purchase options. A successful checkout redirect is not proof of payment or a credit grant; wait for the server-confirmed ledger. Staging uses Stripe TEST, not live commercial payments. Cancellation stops renewal under the paid-term rules shown in Billing; it does not erase historical scans or silently convert remaining credits into money.

Refer & Earn is in the account/billing navigation. Ordinary customer referrals can earn a one-time 5,000-credit reward after a qualifying new organization's paid subscription and 30-day hold; reward credits expire six calendar months after grant and need active paid access to spend. New approved-promoter referrals earn eligible cash commissions instead, not both rewards. Eligibility, review holds and reversals apply; promoter payouts require manual owner review. Do not describe pending credit rewards as withdrawable cash or promise a reward merely for signup.

Account & privacy contains storage/marketing choices, authorized data export and reviewed export/deletion requests. A deletion request is not instant erasure and does not automatically cancel a subscription; manage renewal separately in Billing. Respect the displayed request status. Workspace membership does not grant platform-admin access; owner-only financial/tester controls retain their separate authorization and MFA checks.

Why credits may not be spendable yet

Live work also needs active authorized account access, valid setup, an available module/mode, current permissions and provider-spend protection. Approved testers can use eligible owner-granted credits under the tester policy without fabricating a paid Stripe subscription. Their expiry, module/mode limits and genuine provider safeguards still apply.

Provider spending in USD is a separate safety budget from VIDIK360 credits. Do not infer dollars from the credit balance. A paused/expired authorization, suspended account, missing setup or exhausted provider allowance is not fixed by hiding a banner. Follow the specific review reason or ask the owner to inspect the relevant control.

Viewing saved reports, competitor comparisons, evidence, filters and deterministic exports does not consume scan credits or trigger fresh collection. A copied LLM prompt neither authorizes spending nor starts a run.

Network top-three metrics

Worked example: six planned checks; four valid checks with owned slot counts 2, 3, 0, 1; one failed and one missing. Completeness is 4/6. Top-three coverage is 3/4 = 75%; two-slot coverage 2/4 = 50%; full-pack coverage 1/4 = 25%; slot ownership 6/12 = 50%. The failed/missing checks are unknown, not losses.

A 3/3 sweep applies to one query at one point in one observation. Never combine different keywords or points to create it. Network best rank is the best distinct owned listing per check, not an average of each brand's average. These overlapping percentages are not market share, traffic share or proof of sales; they need not sum to 100%.

• Top-three coverage = eligible valid checks with at least one owned listing in positions 1–3 ÷ all eligible valid checks.
• Two-slot coverage = eligible valid checks with at least two distinct owned listings in positions 1–3 ÷ all eligible valid checks.
• Full-pack coverage = eligible valid checks with three distinct owned listings occupying positions 1–3 ÷ all eligible valid checks.
• Top-three slot ownership = distinct owned top-three slots across eligible checks ÷ (3 × eligible valid checks). Stable listing identifiers and distinct positions prevent duplicate counting.

Average Rank Position (ARP): found only

Sum the observed best ranks for the selected business/domain, then divide by checks where that entity was found. Show found checks alongside total valid checks. Ranks 2 and 8, plus one valid absence, yield (2 + 8) / 2 = 5.00, found in 2 of 3 valid checks. No found checks means unavailable, not zero.

ARP can look better when weak positions disappear, because absent checks do not enter its average. Always read it with coverage and completeness. No AI ordinal rank is calculated. Maps and organic Search remain separate; these descriptive definitions do not claim equivalence with another vendor's named metric.

Average Total Rank Position (ATRP): top-20 cap

For each eligible observation use the actual rank in positions 1–20, or 21 when verified evidence establishes that the entity is outside the top 20. Divide the sum by those depth-eligible checks. For ranks 2, 8 and a verified outside-top-20 result: (2 + 8 + 21) / 3 = 10.33. The 21 is a calculation convention, not an observed rank.

Requested depth alone does not prove retrieval. The evidence must establish the cutoff through verified returned depth or a supported explicit exhausted-result contract. A plain short/empty response does not suffice. Failures, pending/uncollected, ambiguous/malformed checks and insufficient-depth observations are excluded; no eligible checks means unavailable. Read depth exclusions and completion counts.

Unique eligible checks have equal weight; no search volume is invented. In a network view the same calculations use best owned rank per observation. A comparison needs compatible paired queries, locations, devices, languages, platforms, tracking/parser settings and cutoff. Found-only changes use pairs found in both runs; capped changes use pairs eligible in both. One run does not establish a weekly trend.

You vs competitors

Your network or selected brand stays first, followed by up to five external competitors supported by the selected filters and evidence. All known owned brands remain excluded from the external list even when you select only one. Open a competitor for supporting checks; View all shows the rest.

Maps defaults to top-three coverage with top-10/top-20 options. SEO defaults to top-10 organic coverage with top-three/top-20 options. Each business/domain counts once per eligible check, using its best position. Different Maps branches with distinct identifiers are not merged merely because they share a website. Organic pages group by the application's domain identity rules, preserving meaningful hosted-site identities.

Competitor coverage needs adequate retrieval evidence for its selected threshold, so its denominator can differ from the main network summary. Failed, ambiguous or unavailable evidence is excluded, not a zero. Percentages do not sum to 100%. Changes are percentage points over paired compatible checks, not market-share changes.

For Maps and organic Search, the owned row measures the businesses tracked in that saved scan within the competitor-eligible checks. Historical or disabled owned identities still keep your businesses out of the external-competitor list; they do not add new measured wins to an old scan.

AI competitor mentions use stored answers and supported known/reviewed identities; a partial known-competitor watchlist is not exhaustive discovery. Mention coverage and used-source citations are separate. Cited publishers/directories belong in Cited sources, not automatically in a list of competing businesses. Keep platforms and answer sample counts visible.

Choose evidence before conclusions

Check the selected run/date, keyword, location, brand and platform. Open a result for its exact query, timestamp, coordinates/context, matched identities and evidence. A result can be live, imported provenance where supported, or an explicitly labelled sample; sample data does not verify your business.

Reports preserve a snapshot of their selected scope. Choose the implemented module combination and inspect date, freshness, partial status and denominators. Saved reports do not become current just because you open them again. Shared links remain subject to permissions, expiry and revocation; do not paste private links into an LLM.

A changed grid, keyword set, business identity or platform can change coverage without a ranking improvement. Use the comparable subset and exposed pair counts. A missing baseline or incompatible history should be reported as unavailable rather than filled with a trend.

Follow the same run

Submitted/queued means work is accepted or waiting for admission. Running can include waiting for provider readiness; Standard collection is asynchronous. Partial/failed means inspect individual check status and exclusions. Completed describes collection, not a guarantee of a match or a ranking improvement.

You may navigate away and return to the same run. Use its persistent status and saved evidence. A network timeout after clicking Run does not prove the run failed to start. Recover/check the original attempt or existing run before creating a new one. Never use a second run as a substitute for polling.

Configure recurring work only when permitted

Scheduling requires its own available entitlement, enabled schedule and approved spending limits. Tester/manual authorization does not automatically permit schedules. Saving setup, imports or a tracking-plan forecast never silently enables recurring paid work.

Review the actual timezone, cadence, next run, mode and forecast. Weekly is not exactly four runs per month; some periods contain five. The displayed period and actual occurrences determine the estimate. Daylight-saving rules use the configured timezone; a scheduled time is not an exact completion promise.

Insufficient eligible credits or budgets stop new submissions without shrinking your chosen coverage. Pause/resume explicitly and check the next due occurrence; do not assume missed paid scans will replay as a backlog. Already purchased known tasks may still be retrieved safely when new spending is paused.

Setup or entitlement problems

• Not ready: check the module's enabled businesses, terms and locations. Saved disabled rows are drafts. Search needs a valid owned domain; Maps does not. Use the specific field action, save, then reopen review.
• Workspace/business/website limit: inspect saved items across projects and the current account entitlement. Ask the owner to review a legitimate tester allowance when needed. Credits are not a bypass; do not create duplicate accounts or delete history to evade a limit.
• Paid scans off / module or mode not included: read current live-access status, expiry and budget reason. Ask the owner to activate/review the appropriate tester access; a balance alone does not authorize a scan. Do not invent a subscription or widen a restricted policy.
• GOOGLE_AI_PRICING_UNAVAILABLE: selected Google AI collection is draft-only under the current policy. Explicitly choose available ChatGPT/Gemini with a valid shared market, or Gemini-only for a city context; save the choice and request a fresh quote. Do not assume Google AI Mode equals Gemini.

Provider location rejection: 40501 / location_name

Check the provider-location field, not only its display label. For supported SEO/Gemini Toronto use Toronto,Ontario,Canada; for ChatGPT use a supported country/region such as Canada. New plans normalize spaces around commas, but cannot make an unsupported city or misspelled market valid. Verify unfamiliar names rather than guessing.

Keep the failed run and its accounting history intact. Correct the saved setup, obtain a new quote and intentionally create a new run only after confirming the old failure is definitive. No result was collected merely because the request appeared in History. A rejected request does not prove that a business is absent from rankings.

Loading, access and interruption

• Loading recorded checks / database operation failed / HTTP 503: preserve the current run ID, use Retry or reopen that same saved run, and report the displayed request ID if it continues. A summary can load before its paged evidence. Do not start a duplicate paid scan to repair a read error.
• Unknown submission outcome or held reservation: stop manual replacement attempts and request reconciliation. An accepted provider task can exist even if the browser did not receive a response.
• Session expired / forbidden: sign in again and verify the correct workspace membership. A fresh login cannot grant access to another tenant. Confirmation/recovery links can be single-use or expire; request a fresh link through the app instead of sharing the URL or token.
• Basemap unavailable: saved points and the list can remain usable. Check the map status, permitted style and network; an isolated tile failure is not a ranking failure. Do not change coordinates or rescan to fix imagery. Required attribution remains visible.
• Stale draft / version conflict: review the server's saved configuration before applying your edits again. Do not overwrite another editor's changes blindly. A retry should preserve the original import or scan attempt identity where the app offers recovery.

Share a safe support report

Include the page, approximate time/timezone, module, action, exact error code/request ID and authorized run ID where available. State whether the problem is saving, quoting, starting, progress or reading evidence. Redact screenshots. Never send passwords, API keys, session tokens, payment details, confirmation links or raw private customer exports to an LLM or public issue.