The contact request work, done and queued for one look
It reads every contact request your EasyBroker account holds, drafts the changes that follow, and hands you a card for each one before a single contact request moves.
Open the contact request. Check it against something else. Write the change. Move to the next one. That is the EasyBroker afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a contact request until you approve it.
What it can do is exactly what EasyBroker exposes to an account you authorise and nothing beyond it: 6 operations, 4 reads and 2 writes. In practice that means it can create a property and create a contact request, and work across the contact requests, properties and contacts.
The EasyBroker API stops at EasyBroker. 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.
Can it list property types on its own?
4 of the 6 operations are reads.
Your account, not a guess at it: a companion can list property types, list contact requests and get a property, and the full list below is the whole list, with nothing inferred from EasyBroker's documentation.
The contact requests are what most of this inventory is about, alongside the properties. A companion can hold all 6 of these operations and forty open tabs in the same pass, which is how an afternoon of EasyBroker admin becomes a queue you review.
- List Property Types
- List Contact Requests
- Get Property
- Get Contact
Who signs off on a new property?
All 2 write operations wait for you.
A companion can create a property and create a contact request, and each one is staged on an approval card first: you see the contact request, the field and the new value before it lands in EasyBroker.
Nothing in EasyBroker is sent, changed or deleted on your behalf without that click, and a rejected card leaves the contact request exactly as it was. The gate is the same one on every surface, described at security.
- Create Property
- Create Contact Request
Can it create property on a schedule?
Yes.
Saved as a routine, the EasyBroker contact requests 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 EasyBroker contact requests 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