# ACI

> Planned: send inspection details from your texts into ACI appraisal software.

Status: Coming soon

Source: https://asktack.com/docs/integrations/aci/

**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 ACI:

| You text | What would happen in ACI |
|---|---|
| "44 Elm: 3 bed, 2 bath, 1,850 sq ft" | 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

Identify the exact product: ACI Report desktop and ACI Sky are different environments. ACI documents specific integrations and report-data exchange, but that is not evidence of a general public write API. For example, its [Research documentation](https://www.aciweb.com/kb-categories/research/) covers comparable-data import/export.

## Developer setup — vendor approval first

1. Ask ACI for the supported third-party route for importing field notes, photos and draft report fields into the customer's product/version.
2. Request developer/partner eligibility, SDK or file-format documentation, sample files, licensing and a test environment.
3. Confirm whether the approved route is a local plugin, file import or hosted API. Obtain the authentication, permission and revocation instructions for that route.
4. Define field mappings and round-trip behavior using vendor samples. Do not assume an existing integration's access is available to a new developer.

## Customer setup — after a route is confirmed

1. Have the appraiser/admin provide product name, version and license details, plus the workstation or hosted account involved.
2. Enable/install only the vendor-approved integration. Use local admin help if a desktop component is required.
3. For a file-based route, choose approved exchange folders and access permissions. For an API route, authorize the customer account through the vendor's documented process.
4. Back up a test appraisal and agree on exactly which fields and photos may be changed.
5. Keep signing, certification and report delivery separate from draft data entry.

## Verify write access

Import or write a small sample into a copy of a report. Have the appraiser compare every affected field and image, reopen the report and confirm saved changes. Repeat to detect duplication and verify the original can be restored. Do not use a live signed report as the first test.

## Disconnect and unresolved details

Use the confirmed route's uninstall/revocation process, remove local secrets and withdraw exchange-folder access as appropriate. Verify reports remain usable. Exact API endpoints, customer authorization screens and supported draft-write operations are still vendor-dependent; the next step is obtaining ACI's approved integration documentation.

## 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._