Supplier coordination: request, clarify, compare
A procurement assistant can send a defined request to approved suppliers, collect their replies, and ask for missing delivery or pricing details. Each incoming response becomes evidence for the comparison presented to the owner.
Inbox role: a stable project address, separate supplier conversations, and access to replies. Application role: matching offers to the request, validating extracted numbers, tracking deadlines, and collecting approval before accepting an offer.
A useful success measure is the proportion of requests with complete, reviewable answers. Counting sent emails alone does not tell you whether the agent completed useful work.
Customer support: collect the missing information
A support agent can ask a customer for a reproduction step, an order reference, or a screenshot, then continue the same case when the answer arrives. An unresolved conversation can be handed to a human with its message history.
Inbox role: customer replies and a consistent contact address. Application role: case ownership, customer identity checks, internal record access, escalation, and limits on refunds or account changes.
Use a dedicated agent mailbox when you want a new support identity. Use an existing mailbox integration when continuity with an established support inbox is the requirement.
Document collection: know what is still missing
An operations agent can request a document from a known contact, associate the reply with the original request, and flag an absent reference or unreadable attachment. The next message can ask only for the missing information.
Inbox role: receiving the document and retaining the request. Application role: safe attachment handling, extraction, validation, storage policy, and permissions for the resulting records.
For Cyberpigeon, inbound attachment access depends on the activated provider and its temporary download URLs. Outbound attachments are not currently supported. Do not design a workflow around an unshipped capability.
Scheduling and project coordination: close the loop
A coordination agent can collect availability from participants and follow up on unanswered questions. A project assistant can request a progress update and summarize the replies for the project owner.
Inbox role: communication with participants who can reply using email. Application role: time zone handling, calendar permissions, conflict detection, and approval before creating or changing a commitment. An email inbox by itself does not grant calendar access.
Account onboarding: handle an expected invitation
An authorized agent can wait for an invitation or email verification message tied to a specific account setup. Your application associates the expected message with that task, checks the destination service, and uses the link or code only within the granted scope.
Do not treat an unexpected password reset or sign-in message as permission to act. The sender, task, destination URL, and account must make sense together. The verification flow belongs to the external service; Cyberpigeon provides mailbox access.
The implementation pattern behind these workflows
- Assign an identity. Provision a mailbox for the continuing role or project.
- Grant access. Give the agent a mailbox key with the scopes it needs.
- Send an authorized request. Persist the business action and an idempotency key before calling the API.
- Resume from an event cursor. Retrieve the message and the application’s saved task state.
- Validate and decide. Separate email content from trusted operating instructions.
- Reply or escalate. Apply the owner’s approval rules, then save the resulting state.
Cyberpigeon exposes durable event polling, rather than customer-configurable push webhooks, in the current beta. Your worker decides how often to poll and when to resume an agent. See the event polling example.
Evaluate the completed task
Measure completion rate, time to a usable answer, unnecessary follow-ups, duplicate sends, and the rate of human escalation. Review a sample of full conversations. A correct API response does not prove that the agent understood the email or had authority to act on it.
These are example application designs, not prebuilt Cyberpigeon automations or customer case studies. Cyberpigeon is in private beta and mail activation is in progress. Start with the API guide and the platform comparison to check fit.