# a la mode TOTAL

> Planned: send inspection details from your texts into a la mode TOTAL.

Status: Coming soon

Source: https://asktack.com/docs/integrations/alamode-total/

**Status: planned — not available to connect in Tack yet.** These steps prepare the integration; creating vendor credentials does not enable it in the app.

## Planned workflows

Planned for a la mode TOTAL:

| You text | What would happen in a la mode TOTAL |
|---|---|
| "44 Elm: 3 bed, 2 bath, 1,850 sq ft, new roof 2024" | Fills those details into the report |

These are intended workflows, not a guarantee that every operation is exposed by the vendor. Each must pass the API and permission checks below before release.

## Before you start

TOTAL is a desktop appraisal workflow. a la mode describes a **TOTAL API** for TOTAL Store merchants, while **TOTAL Connect** handles delivery/order plugins. Neither establishes a generic customer OAuth connection for arbitrary report editing. [TOTAL Store FAQ](https://help.alamode.com/kb/guide/en/6011-total-store-faq-3PBV5P7C6y/Steps/4256971), [TOTAL Connect FAQ](https://help.alamode.com/kb/guide/en/9707-total-connect-faq-yBBO8ed3fB/Steps/4257169).

## Developer setup — vendor approval first

1. Contact the TOTAL Store merchant/developer program with the intended workflow: importing field notes, photos and supported report fields into a draft.
2. Obtain the current SDK/API package, supported TOTAL versions, redistribution terms and sample integration.
3. Ask which operations require a local Windows component, which forms/fields can be written, and how users select the destination report.
4. Implement the approved extension/import mechanism and document installation, updates, backups and uninstall. Do not treat delivery-plugin access as permission to edit any report.

## Customer setup — after the extension is approved

1. Identify the Windows workstation, TOTAL version, license and required plugin entitlement with the customer's administrator.
2. Install the approved component using vendor instructions. The customer signs in locally; do not collect their desktop login through text.
3. Choose a local test report and back it up. Configure the permitted input/output folders if the approved integration uses file exchange.
4. Map note, photo and form-field destinations with the appraiser. Keep report signing and final delivery under explicit human control.
5. Record the installation version, workstation owner and recovery instructions.

## Verify write access

Import a sample note and photo into a copy of a report. The appraiser verifies field placement, image order and that existing content was not overwritten. Repeat the import to check duplicate handling and demonstrate restoring the backup. Only then test a more complete draft.

## Disconnect and unresolved details

Disable/uninstall the approved extension and remove any local credentials or exchange-folder access it created. Confirm TOTAL still opens the original reports. Exact SDK calls, installation package and supported write fields await merchant-program access; no ready-to-use Tack plugin is currently available.

## Who completes the work?

An agent/developer can implement the connector, field mappings and automated checks. A customer administrator must authorize account access and permissions; the vendor must approve any restricted partner access. A business operator verifies the test records before production use. Follow the [shared setup and release checklist](https://asktack.com/docs/integration-setup/) for credential handling, approval gates and launch checks.

_Setup guidance reviewed October 23, 2026. Vendor menus and entitlements can change; unresolved details are called out above._