Hand the SlickText contacts to a companion
SlickText exposes 3 operations and a companion can work all of them: edit a contact, create a contact and add contact to lists. Anything that changes a record waits for your click.
Open the contact. Check it against something else. Write the change. Move to the next one. That is the SlickText afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a contact until you approve it.
What it can do is exactly what SlickText exposes to an account you authorise and nothing beyond it: 3 operations, no reads and 3 writes. In practice that means it can edit a contact, create a contact and add contact to lists.
The SlickText API stops at SlickText. 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.
Does it read the contacts or ask you for them?
In the tab.
SlickText exposes no read operation to a connected account, so a companion opens SlickText in the session you are already signed into and reads the screens you would.
The contacts are what most of this inventory is about, alongside the contacts. A companion can hold all 3 of these operations and forty open tabs in the same pass, which is how an afternoon of SlickText admin becomes a queue you review.
What happens before it can edit contact?
All 3 write operations wait for you.
A companion can edit a contact, create a contact and add contact to lists, and each one is staged on an approval card first: you see the contact, the field and the new value before it lands in SlickText.
Nothing in SlickText is sent, changed or deleted on your behalf without that click, and a rejected card leaves the contact exactly as it was. The gate is the same one on every surface, described at security.
- Edit Contact
- Create Contact
- Add Contact To Lists
Does the contact sweep have to be asked for every time?
Yes.
Saved as a routine, the SlickText contacts 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 operations playbook catalogues the other recurring shapes of the messages, the SlickText contacts 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