MapIntel Pro Universe 4.6.8-u10.17 — Complete User & Operator Guide

This guide describes the features that exist in the supplied 4.6.8-u10.17 source tree. The desktop, website/mobile PWA and Cloudflare API share the same account/module model, but hardware-local work stays on the Windows desktop.

1. Which MapIntel product does what

2. First start from the source ZIP — no Python installation required beforehand

1. Extract the entire ZIP into a normal writable folder. Do not run it inside the ZIP preview.
2. Keep the internet connected for the first start.
3. Double-click START_HERE.bat at the top level. You may also run MapIntelPro\START_MAPINTEL.bat; both use the same self-healing runtime path.
4. Watch the progress bar. Startup first checks the private MapIntel Python runtime, then any compatible 64-bit Python 3.10–3.12 already installed.
5. If no compatible Python exists, MapIntel downloads the pinned 64-bit Python 3.12.10 installer from python.org, verifies its SHA-256 and Python Software Foundation Authenticode signature, and installs it only for the current Windows user under %LOCALAPPDATA%\MapIntelPro\Python\3.12.10.
6. MapIntel then checks only the packages required by the screen being opened. Missing packages are installed into the current-user MapIntel runtime, not into the user's global Python.
7. Discovery/WhatsApp browser components are checked next. If a compatible browser runtime is unavailable, Playwright Chromium is prepared under %LOCALAPPDATA%\MapIntelPro\Browsers.
8. Preflight runs. If it passes, MapIntel Home opens maximized.
9. The first preparation can take longer because Python, packages and the private browser may need to be downloaded once. Later starts reuse them.

If startup cannot finish

• Run REPAIR_AND_START.bat from the top-level folder.
• REPAIR_AND_START.bat performs the current-user runtime repair and starts MapIntel again.
• Runtime repair does not intentionally delete CRM, Discovery, WhatsApp or account business data.
• Useful support files are %LOCALAPPDATA%\MapIntelPro\logs\startup-console.log, %LOCALAPPDATA%\MapIntelPro\logs\startup-diagnostic.json and %LOCALAPPDATA%\MapIntelPro\logs\missing-dependencies.log.
• Python absence is a bootstrap condition, not a user prerequisite. Since u10.16, startup, module preparation and support logs outside the extracted source tree under the current Windows user profile.

3. Sign in and MapIntel Home

1. Open MapIntel Home.
2. Enter the account mobile number or email and password.
3. Use Show/Hide only when you need to verify the password visually.
4. Use Forgot password? for the website credential-recovery journey.
5. Use Check connection if sign-in does not progress.
6. After authentication, the credential surface is removed only after the secure local session is saved; Home becomes visible again before the background module-seat refresh begins.
7. Open Discovery, CRM or WhatsApp Connect from Home. Home keeps showing the real preparation phase until the selected workspace reports ready. Each paid module obtains its own module-seat lease; opening one module does not consume or close a different module's seat.
8. If the same module seat is active on another computer, MapIntel can offer a deliberate takeover. A takeover targets that module rather than every MapIntel product.
9. Temporary network uncertainty uses the bounded offline/session rules in the client; it is not treated as a fabricated paid entitlement.
10. Use Sign out when the account itself should be ended. Closing a module releases that module's lease without automatically signing out the common account.
11. If sign-in succeeds but module access cannot be checked, select Refresh. A source/developer deployment must run the matching u10.17 API/D1 release. The desktop intentionally does not invent paid seats when an older cloud service lacks the module-seat API.

4. MapIntel Discovery

Start research

1. Open MapIntel Discovery.
2. In Discovery queries, enter one Google Maps/business search per line.
3. Set Wait after each lead only when additional pacing is desired. 0 means no extra wait.
4. Choose the browser mode offered by the Discovery screen. Installed Brave/Chrome/Edge can be used when available; the current release can fall back to the private MapIntel Chromium automatically.
5. Select Start discovery. Do not repeatedly click Start; the UI prevents a second active run.
6. The engine saves completed query progress locally. Cloud upload is separate so a cloud problem does not have to erase local research.

Control a run

• Pause: safely pauses the active run and releases critical resources where applicable.
• Resume: continues pending work after a pause.
• Stop: requests a controlled stop and browser shutdown.
• Keyboard shortcuts exposed by the Discovery GUI include Ctrl+E Start, Ctrl+P Pause, Ctrl+R Resume and Ctrl+X Stop.
• F5 refreshes the current workspace, Ctrl+F focuses the primary field and F11 toggles the maximized/full-screen presentation where supported.

Results and maintenance

• Open results folder opens the local Discovery output location.
• Secure Cloud Sync / Sync cloud data retries the cloud queue without deleting local export records.
• Clear discovery history is a separate explicit action from starting or syncing research.
• System Health & Diagnostics is available from Help for freezes, crashes, memory/resource alerts or repeated network failures.

5. Customer CRM

CRM workspace

1. Open MapIntel CRM.
2. Use the search field to search customers, contacts, invoices or notes.
3. Use the table headers to sort supported columns.
4. Use Previous/Next for paged tables rather than loading an unlimited row set into the GUI.
5. Select a customer to enable record actions.

Customer actions

• Add customer opens the customer/note dialog.
• Customer information is separated into contact/business/follow-up details rather than one long form.
• A follow-up can use a preset choice or a custom YYYY-MM-DD HH:MM date/time.
• Open customer opens the selected record.
• Edit edits the selected customer.
• Add invoice starts an invoice for the selected customer.
• Copy summary copies the customer summary.
• Call, WhatsApp Web and Email use the selected customer's available contact details.
• Delete selected uses the permanent-deletion verification contract rather than assuming that any HTTP success means the cloud record is gone.

6. Invoices, receivables and CRM payment reminders

Invoice meaning

• Invoice date is the accounting date used by the sender.
• Positive current balance means the customer owes money.
• Negative current balance means advance/credit and is not treated as a receivable.
• Due date for a reminder run is calculated from invoice date + credit days selected in that sender run.
• Tally's imported due date/credit period is not used as the final reminder due-date authority in this workflow.

Invoice manager

1. Open Invoices & reminders / Invoices and WhatsApp sender.
2. Search by customer, invoice number or PO reference.
3. Use Add invoice, Edit selected, Refresh or Open sender for selected invoice.
4. Pagination keeps the full dataset calculation separate from the visible page.

Payment-reminder sender — three steps

1. Choose customers: choose credit days, overdue range and customer groups. Credit-only/advance customers remain excluded from owing-customer reminders by default.
2. Prepare message: choose identity wording, edit the WhatsApp message, insert supported customer/invoice fields, configure document links/attachments and set sending pace.
3. Review customers: inspect the exact calculated audience and start only from the final review.

Available sender controls include:

• standard/custom credit days;
• minimum/maximum overdue days and due/upcoming ranges;
• customer-group selection;
• message field insertion;
• per-customer secure pending-invoice PDF link;
• optional complete ledger-history PDF;
• secure-link expiry;
• ordered direct attachments;
• customers-per-batch and rest-after-batch pacing;
• Connect / verify WhatsApp;
• Forget saved login;
• Pause after customer, Resume sending and Stop after customer.

The visible WhatsApp Web browser is used for the Existing Number-style CRM payment reminder journey. A pause/stop takes effect after the current customer so the contact result can be recorded coherently.

7. CRM Import & MapIntel Bridge

Open CRM → Import / Tally. Every import first prepares a preview; saving happens only after Import now.

Files

Supported chooser types in this release include CSV, TSV/TXT, Excel (xlsx, xls, xlsm, xlsb), ODS, JSON/JSONL/NDJSON, XML, DBF and Parquet. The file screen supports:

• Excel sheet selection;
• header-row selection;
• Auto/Comma/Tab/Semicolon/Pipe delimiter;
• Auto/UTF-8/UTF-8-SIG/CP1252/Latin-1 encoding;
• account-country default for blank country codes, with row-level override;
• a 100 MB / 100,000-row per-run guard in the GUI contract.

Web/API source

1. Enter an HTTPS remote file, REST API or published sheet URL.
2. Choose GET or POST.
3. Add optional request headers as JSON and optional POST body.
4. Saved authentication headers/request bodies use encrypted local source configuration rather than being copied into cloud source metadata.
5. Review and import.

Direct Tally

1. Keep TallyPrime open with a company loaded.
2. Enable its HTTP server on the configured port (default UI value 9000; other configured ports are accepted).
3. Use 127.0.0.1 when Tally is on the same PC, or the LAN/VPN IP when it is on another computer.
4. Enter the company name when exact selection is required; blank can use the currently loaded company.
5. Choose Automatic (XML first, ODBC fallback), XML over HTTP, or ODBC only.
6. Add the ODBC connection string only when that path is used.
7. Use Check Tally connection, then Review & import.
8. The connector reads group hierarchy/ledger Parent classification, contact information and open receivables into the review model.

SQLite / local database

1. Choose a .sqlite, .sqlite3 or .db file.
2. Inspect tables.
3. Choose the table.
4. Review/import.

Generic ODBC

1. Enter a connection string for an installed ODBC database driver.
2. Enter one read-only SELECT or WITH query.
3. Write/DDL/procedure and multi-statement commands are rejected by the import path.
4. Review the returned rows before import.

Import preview

• Automatic field matching is proposed first.
• Refresh preview reruns validation when needed.
• Tally/connector fields can be remapped without changing protected stable record/link identifiers.
• Standalone Tally Bills Receivable XML can use the explicit group assignment for still-unclassified customers.
• Optional snapshot reconciliation should only be used for a complete latest outstanding snapshot; incomplete/failed chunks withhold snapshot closure.
• Remembered sources can later be manually synced, paused/resumed for automatic refresh, inspected for run history or disconnected.

8. WhatsApp Connect — data model and navigation

WhatsApp Connect is intentionally independent from CRM. Its contacts, lists, templates, method histories, campaigns and reports are stored in the WhatsApp workspace. CRM data is not silently treated as a WhatsApp contact list.

Desktop navigation contains:

1. Overview
2. Smart Method
3. Unified WhatsApp inbox
4. Contacts & lists
5. Official Meta Method
6. Virtual Number Method
7. Existing Number Method
8. Message templates
9. WhatsApp automations
10. Sync Center
11. Campaign reports
12. Automatic resource coordination

The three source methods keep independent histories. Smart Method and Unified Inbox are operational/merged layers; rebuilding or disabling merged sync does not mean deleting the original method histories.

9. Contacts & lists

1. Open Contacts & lists.
2. Use Add contact for a single record or Import Excel / CSV for a batch.
3. The WhatsApp importer supports CSV, XLSX, XLS, XLSB, ODS, TSV and TXT.
4. Choose a list name and default country.
5. Select Numbers already contain international country codes when appropriate.
6. Select Use a Country column when present when the source has row-level countries.
7. Review the inspected result before Import clean contacts.
8. Duplicate/invalid rows are kept outside the clean contact save; invalid rows can be exported for correction.
9. Search contacts by name, phone, email, list or notes.
10. Select a page, clear selection, move contacts between lists, or export WhatsApp contacts to CSV.

10. Smart Method

Smart Method starts one campaign and chooses among suitable configured methods while preserving a decision/attempt/cost record.

1. Open Smart Method.
2. Choose a contact list.
3. Choose the Smart Method preference.
4. Decide whether Official Meta may be used only when MapIntel has verified a recent inbound active customer conversation. Approved first-contact template campaigns remain better started explicitly from Official Meta Method.
5. Enter the message. {name} and {phone} personalization is performed locally for the Smart campaign.
6. Review/update the per-method cost card when required.
7. Select Review & start Smart campaign.
8. Use Stop safely to stop after the current recipient boundary.

Recipient locking/idempotency prevents the same unified campaign recipient from being accepted twice through a second operation identity. Method fallback is allowed only when the prior attempt is known not to have produced the messaging side effect.

11. Unified WhatsApp inbox

1. Open Unified WhatsApp inbox.
2. Search by name, number or recent message.
3. Select a conversation to inspect its messages.
4. Every merged message retains its original method/source identity.
5. Use Sync now for Official Meta catch-up plus local-method merge.
6. Use Mark read where available.
7. Use Open sender to continue from the appropriate method context.
8. Use Export to export the selected conversation to CSV.

12. Official Meta Method

The only supported Official Meta architecture is desktop/web → MapIntel API/Cloudflare Worker → Meta Graph API. Users do not choose a second transport and do not paste permanent Meta tokens into the desktop.

Connect

1. Open Official Meta Method.
2. Select Connect on MapIntel / Connect Official Meta to open the secure web Embedded Signup flow.
3. On the web connection page, enter a 6-digit Cloud API registration PIN before choosing Connect Official Meta. MapIntel uses it only if Meta reports that the selected phone number still needs registration; the PIN is not saved in the browser or stored with the connection.
4. The desktop intentionally has no transport selector or permanent Meta-token fields. Official Meta uses the MapIntel API connection only.
5. Refresh connection verifies the connected business through the MapIntel API and does not send a customer message.
6. Sync templates refreshes approved Meta templates into the local WhatsApp store.
7. Remove connection removes the connection configuration while preserving existing WhatsApp history.

Send

• Official Meta supports approved templates, eligible active-conversation text and supported media flows represented by the cloud API.
• Logical operation/idempotency keys are reused for uncertain retries so an unknown response is not blindly transformed into another business send.
• Delivery/read/failed updates reconcile monotonically so a late older webhook does not downgrade a later confirmed state.

Web/mobile

The browser WhatsApp page can connect Official Meta and perform the cloud-safe Official Meta operations while the office computer is off, because the final Graph call and webhooks live in the Cloudflare control plane.

13. Existing Number Method

Use this desktop/browser method for existing customers or prior respondents.

1. Open Existing Number Method.
2. Open Connection & session.
3. Select Connect / verify. MapIntel opens a full WhatsApp Web browser only when needed.
4. Complete QR login when no saved profile exists.
5. The profile is retained for this Windows user.
6. Use Switch WhatsApp account when the phone account changes.
7. Use Logout and delete saved session files to remove the locally stored WhatsApp Web session.
8. In Campaign setup, confirm the audience condition shown by the UI, choose the WhatsApp contact list, template/message mode, message and attachments, then review.
9. Use Review & start, Pause after current, Resume and Stop safely.
10. Images, profile photos, video/audio/documents/fonts and normal WhatsApp Web service-worker/network behavior are not intentionally content-blocked in this method.

The current release can use the private MapIntel Playwright Chromium when no suitable installed browser is available.

14. Virtual Number Method

1. Open Virtual Number Method and its provider automation settings.
2. Save the provider dashboard URL/mapping required by the configured provider contract.
3. Use Save & open dashboard and sign in once in the provider browser.
4. Use Save & test mapping before a production campaign.
5. The provider browser keeps its own local browser profile and history separate from Existing Number and Official Meta histories.
6. Use Delete saved browser session when that provider login must be removed.
7. Campaign sending uses the same controlled review/pause/stop/report concepts, but actual provider success must be positively evidenced. Lack of positive success is not labelled as a confirmed send.
8. The current release can fall back to private MapIntel Chromium if a compatible installed browser is unavailable.

15. Message templates

1. Open Message templates.
2. Create/edit a template name, available method, language/Meta locale and message.
3. Supported local personalization tokens shown by the editor are {name}, {phone}, {business}, {sender} and {message}.
4. Official Meta approved-template name/language/body parameters are handled by the Official Meta campaign mode where relevant.
5. Save and select templates from campaign setup.

16. WhatsApp automations

Current desktop automations are intentionally simple local rules tied to synced Official Meta messages.

1. Open WhatsApp automations.
2. Enter a rule name.
3. Choose the trigger shown by the current build (including incoming/contains/failure variants exposed by the rule UI).
4. Enter match text when that trigger requires it.
5. Choose the action and action value, such as moving/updating the shared WhatsApp contact list/tag state supported by the rule engine.
6. Select Add rule.
7. Rules execute locally after live Official Meta synchronization and preserve the original method message.
8. Select a rule and Delete selected to remove it.

17. Sync Center

1. Open Sync Center.
2. Use Sync all now for a manual catch-up.
3. Receive live updates controls the live Official Meta update behavior exposed by the screen.
4. Rebuild merged view reconstructs the derived/unified view from source method history; it does not mean erasing source histories.
5. Inspect the WhatsApp method status cards for per-method readiness/sync state.

18. Campaign reports

1. Open Campaign reports.
2. Filter by method when required.
3. Page through saved campaigns.
4. Double-click or use Open results to inspect recipient-level results.
5. Use Export results to export the contact-level campaign result data.
6. Delete report… deletes the selected campaign/report data only after its explicit confirmation path.

19. Automatic resource coordination

There is no resource-sharing or performance option for the user. MapIntel decides automatically in the background.

• Foreground work on the current computer always has priority.
• MapIntel prefers the current computer, then suitable same-company MapIntel computers where the built-in job can be safely split.
• Privacy-safe spare capacity is considered only when CPU, memory and power conditions indicate that background work will not disturb normal use.
• Only centrally authorized, signed, allow-listed built-in work units are accepted. Peers cannot send arbitrary Python, PowerShell or commands.
• Sensitive tenant work stays within the tenant target policy; public cooperative work is limited to data classified for that path.

20. Website and Mobile PWA

Sign in/install

1. Open the MapIntel website in a supported modern browser.
2. Sign in with the same account identity used by the desktop.
3. Use Install app / the browser's install-to-device action to install the PWA where offered.
4. The workspace provides Overview, Customer CRM, WhatsApp Connect and Signal Center navigation.
5. Mobile uses the same authenticated workspace semantics with a compact top bar/bottom navigation and account sheet.

Offline and updates

• The service worker caches the application shell needed for the PWA/offline page.
• PWA activation does not forcibly reload every controlled page. It broadcasts activation and lets the application recover without the old surprise-navigation behavior.
• Push-notification navigation is sanitized to same-origin application URLs.
• CRM browser storage/offline outbox state is partitioned by authenticated account; operation replay is not meant to cross into a different signed-in user's session.

Web capability boundary

• CRM views/actions that are implemented through the cloud API can run from browser/mobile.
• Official Meta can use the cloud control plane directly.
• Existing Number and Virtual Number require a Windows browser/provider environment. Browser/mobile requests are therefore written as durable commands and claimed by an authenticated MapIntel Agent on the correct office PC.
• Discovery, direct Tally/local database access and other hardware-local operations remain desktop responsibilities rather than being faked in the browser.

21. Signal Center and push notifications

1. Open Signal Center.
2. Use Refresh to retrieve current administrator announcements.
3. Use Enable admin notices on this device when browser push should be enabled.
4. The browser subscription is tied to the current authenticated account; logout/account replacement invokes the push cleanup path.
5. Business users do not get a customer-push marketing broadcaster from this Signal Center. The supplied browser page is for official MapIntel administrator notices.

22. Account, organisations and module seats

• One identity can own/access multiple entitled modules.
• The selected organisation scopes organisation-owned access and WhatsApp/compute operations where the source applies organisation scope.
• A module-seat lease is separate from the common sign-in session.
• Home can direct the user to account/seat management when a module is not assigned, expired, inactive or out of seats.
• Version-required responses direct the user to the current download/update path.
• Website CRM/offline storage and pending WhatsApp operation identity are scoped so account/organisation changes do not intentionally reuse the previous context.

23. MapIntel Agent

The Agent is the current-user background bridge for work that must continue without holding a front-end window open.

Its current responsibilities include:

• synchronized local/cloud event work;
• durable web-to-desktop WhatsApp commands for Existing Number/Virtual Number;
• command claim/lease/completion and uncertain-outcome recovery;
• cooperative-compute registration/heartbeat/claim/result work;
• bounded synchronization so simultaneous triggers are coalesced rather than running overlapping full sync cycles.

If an unsafe/unknown browser-side send outcome survives a crash, the command recovery path can require review instead of blindly repeating the send.

24. System Health & Diagnostics

Open Help → System Health and Diagnostics.

• Current health summarizes active resource alerts.
• Resource cards expose the current sampled state.
• Send support report now tries to synchronize pending diagnostic events/metrics.
• Save support package exports a diagnostic ZIP.
• Open support folder opens the local diagnostics location.
• Prepare Windows recovery details requests the Windows crash-capture preparation supported by the client.
• Diagnostic design is separate from customer records/passwords/message content; exported support data uses redaction/sanitization controls in the diagnostics implementation.

25. Updates

• The desktop checks the cloud latest-version contract.
• A required newer version opens the current download/update journey.
• Remote HTTPS update packages require the updater's verification/signing contract; interrupted replacement is staged with rollback/recovery rather than intentionally overwriting the live installation piecemeal.
• Production release building requires the release-signing configuration enforced by the build scripts; development builds are explicitly different from signed production release output.

26. Deployment — API and website

One-command deployment preparation on Windows

1. Set the Cloudflare/Pages configuration required by your environment, including MIP_PAGES_PROJECT for the website deployment script.
2. Run DEPLOY_API_AND_WEBSITE.bat.
3. The script prepares the pinned private Node.js runtime when Node is missing, installs the pinned mip-api package tree, performs database deployment/repair steps, deploys the Worker, verifies it, then deploys the website/PWA.
4. MapIntelWebsite\DEPLOY_WEBSITE.bat uses the pinned local wrangler.cmd installed from mip-api; it does not intentionally fetch an unpinned wrangler@latest during every deployment.

The private deployment runtime is Node.js 24.19.0 x64 under %LOCALAPPDATA%\MapIntelPro\Node\24.19.0, verified against the pinned archive SHA-256 before use.

D1 migrations

Historical migrations remain immutable. For an existing accepted 4.6.8 database, the current release chain includes u10.9 Smart/asset-light, u10.10 reliability hardening, u10.11 continuity hardening, u10.12 experience polish, u10.13 self-healing/parity, u10.14 Windows startup assurance, u10.15 zero-friction sign-in and u10.16 post-login module-journey assurance and u10.17 Meta Tech Provider review readiness. Since u10.16, MapIntel also self-heals active module leases whose identity session has already ended. Fresh deployments use the current mip-api\schema.sql; production deployment runs npm run db:ensure so an already-current fresh schema is not blindly replayed through incompatible historical ALTER statements.

27. Cloud/API surface reference

The supplied Worker route map includes these functional groups:

Identity/licensing

/website-register, /website-login, /website-logout, /oauth-login, /set-credentials, /validate-user, /user-login, /logout, /heartbeat, /website-profile, /change-plan, /modules/entitlements, /modules/leases/acquire, /modules/leases/heartbeat, /modules/leases/release, /latest-version.

CRM

/crm/schema-health, /crm/revision, /crm/dashboard, /crm/clients, /crm/clients/:id, /crm/clients/:id/activity, /crm/settings, /crm/import/bulk, /crm/import/sources, /crm/import/runs, /crm/invoices, /crm/invoices/:id, /crm/invoices/:id/send-result, /crm/reminders/due, /crm/reminders/:id, /crm/documents/publish and the signed public customer-document routes.

Notifications

/notifications, /notifications/read, /push-key, /push-subscribe, /push-unsubscribe.

WhatsApp platform

/whatsapp/meta/account, /whatsapp/meta/public-config, /whatsapp/meta/connect, /whatsapp/meta/disconnect, /whatsapp/meta/templates, /whatsapp/meta/messages, /whatsapp/meta/media, /whatsapp/meta/sync, /whatsapp/meta/webhook, /whatsapp/commands, /whatsapp/commands/claim, /whatsapp/commands/complete, /whatsapp/live.

Automatic resource coordination

/compute/register, /compute/heartbeat, /compute/jobs, /compute/claim, /compute/result, /compute/public-key, /compute/status plus the administrator queue endpoint.

Diagnostics/admin/events

/diagnostics/batch, /events/batch, /events, and the supplied authenticated administration routes for overview/users/errors/announcements/versions/audit/diagnostics/broadcast/compute administration.

Website function proxies intentionally expose only the browser-safe subset. Agent-only claim/complete operations are not a reason to expose local browser control directly to a public PWA.

28. Build from source

For a developer producing Windows EXEs/installer:

1. Use BUILD_WINDOWS_EXE.bat at the top level, or MapIntelPro\BUILD_RELEASE.bat directly.
2. The build verifies the accepted source inventory from AUDIT_TRAIL.csv before compiling.
3. The build produces the engine plus MapIntelHome, MapIntelAgent, MapIntelUpdater, MapIntelDiscovery, MapIntelCRM and MapIntelWhatsApp application topology.
4. Inno Setup is a developer/build compiler dependency, not a prerequisite for an end user starting the supplied source or installed application.
5. The customer installer is current-user scoped under %LOCALAPPDATA%\Programs\MapIntel Pro with lowest privileges.

29. Safe Troubleshooting by symptom

“MapIntel needs 64-bit Python 3.10, 3.11 or 3.12”

That was an obsolete source-launch behavior. Since u10.16, rerun START_HERE.bat; the source launcher prepares its private Python automatically. If it cannot download/verify/install, run REPAIR_AND_START.bat while online and inspect the startup logs.

Browser does not open for Discovery/WhatsApp

Run REPAIR_AND_START.bat. The runtime bootstrap checks Playwright and prepares private Chromium for Discovery/Connect when needed. Existing Number keeps full WhatsApp Web resources enabled.

Tally does not connect

Confirm TallyPrime is open, the intended company is loaded, HTTP/XML server is enabled on the configured port, the host/IP is correct and a remote PC firewall allows that private-network port. Use Check Tally connection before import.

CRM import looks wrong

Do not press Import. Return to the preview, change the sheet/header/delimiter/encoding or field mapping, then validate again. For a complete-snapshot option, only enable it when the source truly represents the full latest open-invoice snapshot.

WhatsApp request is queued on web/mobile

Official Meta can run through cloud; Existing/Virtual require the office Agent/desktop environment. Start the correct authenticated office PC and let its Agent claim the durable request.

App becomes unresponsive or crashes

Reopen it, then use System Health & Diagnostics to inspect the health state and save a support package. Startup also records incomplete previous sessions for the diagnostic/recovery path.

30. Important data-separation rules

• Discovery research data is not silently the CRM database.
• CRM and WhatsApp Connect are independent datasets.
• Each WhatsApp Method keeps its own source history.
• Unified Inbox/Smart Method are merged operational layers, not replacements for source histories.
• Existing/Virtual browser profiles remain on the relevant Windows user environment.
• Official Meta long-lived platform secrets/final cloud responsibilities stay in the thin cloud control plane in the recommended architecture.
• Automatic resource coordination accepts only approved built-in work units; arbitrary peer-supplied code is never executed.

31. External production acceptance that still requires the real environment

Source/static/headless tests cannot replace these real-world checks:

• first auto-bootstrap on the target Windows 10/11 machine;
• signed Windows EXE installer/upgrade/uninstall at real DPI/display settings;
• production Cloudflare Worker/D1 concurrency;
• real Meta WABA/Embedded Signup/webhooks/templates/delivery/read events;
• current live WhatsApp Web/provider DOM behavior;
• actual multi-PC sleep/crash/reconnect cooperative/command recovery;
• the customer's real Tally/ODBC/network configuration.

The supplied source has already been audited into AUDIT_TRAIL.csv. Complete these physical gates with the production assets before calling the deployment physically accepted.