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