If you connect SIMCOAI to your own website or systems, you could already send us orders, refunds, bookings and escalations — but not the customer those records belong to. The one thing everything else hangs off was the only thing you could not read or write from outside the dashboard.
You can now list, look up, create and update customer records through the API, and send someone straight from your checkout or booking form into SIMCOAI. Creating a customer is a safe repeat: we match on the email address or the significant digits of the phone number, so replaying your customer list does not create a second copy of somebody already on file, and a blank field you send never wipes a detail we already hold.
Customer records use their own permission, separate from orders and refunds. An integration that only needs to file refunds is not handed your whole contact list with them, and you choose which it gets when you create the key.
Your systems can also be told when something changes rather than having to keep asking. Alongside the existing refund, booking, order and escalation notifications, we now send one when a customer record is created or updated.
What changed
The customer API lets a website or business system work with the customer behind an order or booking. It supports listing, looking up, creating and updating customer records rather than handling only the attached operational records.
A checkout can send contact details into SIMCOAI before a customer calls. Updates can then keep the record useful to the receptionist, while change notifications help integrations respond without repeatedly checking for updates.
Before and after
Before this update: External systems could submit orders, refunds, bookings and escalations, but could not read or write the customer record through this API.
With this update: Customer records have their own API access and permissions. Creation matches existing contact details, and blank submitted fields do not erase details already held.
What it means for you
Give an integration the customer permission only if it needs customer access. Map identifiers carefully and review the returned record when connecting a checkout, booking form or customer system.
Customer access is separate from refund and order access. A key that can file a refund should not automatically receive the contact list; choose the permissions required for the actual integration.