Kustomer StrawberryCustom objects, conversations and customers, worked for you
Hand a companion the outcome. It reads the Kustomer custom objects, does the 8-operation version of the job, and stops for your click on anything that changes a record.
Open the custom object. Check it against something else. Write the change. Move to the next one. That is the Kustomer afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a custom object until you approve it.
What it can do is exactly what Kustomer exposes to an account you authorise and nothing beyond it: 8 operations, 3 reads and 5 writes. In practice that means it can update a customer, update custom object by ID and update a conversation, and work across the custom objects, conversations and customers.
The Kustomer API stops at Kustomer. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Where do the custom objects come from?
3 of the 8 operations are reads.
Your account, not a guess at it: a companion can get custom objects, get custom object by ID and get custom object by external ID, and the full list below is the whole list, with nothing inferred from Kustomer's documentation.
The custom objects are what most of this inventory is about, alongside the conversations. A companion can hold all 8 of these operations and forty open tabs in the same pass, which is how an afternoon of Kustomer admin becomes a queue you review.
- Get Custom Objects
- Get Custom Object by ID
- Get Custom Object by External ID
Who signs off on a new conversation?
All 5 write operations wait for you.
A companion can update a customer, update custom object by ID and update a conversation, and each one is staged on an approval card first: you see the custom object, the field and the new value before it lands in Kustomer.
Nothing in Kustomer is sent, changed or deleted on your behalf without that click, and a rejected card leaves the custom object exactly as it was. The gate is the same one on every surface, described at security.
- Update Customer
- Update Custom Object by ID
- Update Conversation
- Create Customer
- Create Conversation
What does the recurring custom objects pass look like?
Yes.
Saved as a routine, the Kustomer custom objects pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The sales pipeline playbook catalogues the other recurring shapes of pipeline work, the Kustomer custom objects sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents