Skip to content
Signal.

CRM

Reapit, Apex27 and Acquaint: what an AI agent can and can't write back

What an AI enquiry agent writes to Reapit, Apex27 and Acquaint, what it deliberately never touches, and why the line sits where it does.

Photo of Graham Wilsdon

Graham Wilsdon

· 5 MIN

TL;DR

  • The CRM stays the system of record. The agent reads from it and writes to it; nothing lives only in the agent.
  • What gets written: the enquiry, the applicant or contact, every qualification answer, the viewing appointment, the feedback, and a note of each conversation.
  • What doesn’t: anything that changes the property, the vendor or the price. Those are a person’s decisions.
  • The line is a design choice, not an API limit, and it’s the first thing to ask any vendor.

The question every agency should ask

“Where does the data go?” is the right first question for any AI tool in an agency, because the answer determines whether the tool makes the CRM better or quietly replaces it with a second, worse one.

Our answer is that the CRM is the system of record. The agent is a worker that reads from it and writes to it, under rules. If we switched the agent off tomorrow, everything it did would still be in Reapit, Apex27 or Acquaint, in the fields a negotiator would have used.

What the agent reads

  • Listings. Address, price, status, key facts, so it never answers from memory. If a property is under offer in the CRM, the agent knows before the buyer asks.
  • The diary. Available viewing slots per property and negotiator, so it can offer real times.
  • Existing contacts. If the enquirer is already an applicant, the agent picks up the existing record rather than creating a duplicate.

What the agent writes

  • The enquiry, against the right property, with the source.
  • The applicant or contact record: created if new, updated if existing. Phone number, name, and what they’re looking for.
  • Qualification answers, into the fields the CRM has for them: position, finance, timeframe for buyers; affordability, move-in date, referencing readiness for tenants. Where the CRM has no field, a structured note.
  • The viewing appointment, in the diary, with the attendee and the negotiator.
  • Post-viewing feedback, as a note against the viewing, in the applicant’s own words plus a one-line summary.
  • A conversation note at each milestone, so a negotiator opening the record sees what was said and when.

Every write is attributed to the agent, so you can always tell what a person entered and what the system did.

What the agent never writes

  • Property changes. No price edits, no status changes, no amending descriptions. If a buyer says “the listing says three beds but there are two”, that’s flagged to a person.
  • Vendor and landlord records. The agent talks to buyers and tenants. It doesn’t touch the people on the other side of the deal.
  • Offers. It can tell you an offer was mentioned and what was said. Recording and negotiating an offer is a negotiator’s job.
  • Deletions. Nothing is removed. Opt-outs are recorded as a suppression, not a deletion.

These are rules we chose, not gaps in the integrations. An agent that can change a price in your CRM is a liability, however well it’s prompted.

The three CRMs

Reapit, Apex27 and Acquaint each expose a different surface, and each has its own ideas about what an applicant, an enquiry and a viewing are. The work in an integration is mapping our model onto theirs without inventing fields that don’t exist or losing information that does. That mapping is done once per CRM and is the same for every agency on it, which is why connecting a new agency on one of these three takes days rather than weeks.

If your agency is on something else, tell us on the first call. Most CRMs with an API can be mapped the same way; the question is whether it exposes the diary and the applicant record, which are the two that matter most.

How to check a vendor’s answer

Ask three things: what do you read, what do you write, and what will you never write. If the answer to the third is vague, the answer to the first two doesn’t matter.

What we build · Questions agencies ask us