Skip to content
Juni, the Midsummer worker

Home · Matrix · Data and API Companies · Inbound response · vs an outbound agency

vs an outbound agency

Midsummer vs an outbound agency for data and API inbound response.

Two ways to run inbound response for data and API companies. The difference is who approves, and what you can read afterwards.

Midsummer vs an outbound agency for data and API inbound response: An agency sells people doing the work, and when the retainer stops, the capability leaves with them. With Midsummer, every external message waits as a draft until a person on your team approves it, and every action is logged with its source.

The difference

An agency sells people doing the work, and when the retainer stops, the capability leaves with them.

The working law

Whatever the page, the working law does not change: every external message waits as a draft until a person approves it, and every action is logged with its source so you can open it and check. Approval is not a mode you turn on; it is how the department works.

Common questions

Does Midsummer send without approval?

No. Every external message waits as a draft until a person on your team approves it. That is the working law, not a setting.

What can we read afterwards?

Everything. Open any action and read what ran, what it said, and what came back, with the source attached.

What does it need to start?

Read access to your CRM and inbox, scoped in writing at onboarding. Revoke it and the work stops.

Request access