This page is the practical layer: how setup works, how routing works, how feedback works, and where native integrations stop and coexistence or API handoff begins.
How it works
The fastest way to get value is to set up target accounts, signal coverage, and delivery routes intentionally instead of turning everything on at once.
Native delivery means Amplify sends directly into a supported surface. Alongside workflows use a customer-owned system such as Apollo. Handoff workflows use API or webhooks.
Helpful and not-useful feedback is part of the product workflow. It helps the system learn what was useful, what was duplicate, and what needs review.
FAQ
No. HubSpot is the current native CRM integration, but teams can still use Slack, Teams, email, and API workflows without a CRM.
A native integration is directly supported inside the product today, like Slack, Teams, HubSpot, or email. A coexistence workflow means Amplify works alongside a customer-owned system such as Apollo. A handoff workflow means Amplify sends data through the API or outbound webhooks to another system.
Signals delivered in Slack, Teams, and the app include helpful and not-useful feedback paths. That feedback is stored on the event and used for review and learning.
Yes. Competitor monitoring can use a separate Slack or Teams destination so competitor alerts and weekly briefs do not spill into the main rep-facing signal channel.
Use this page as the operational baseline, then talk to us about the exact signal and delivery model your team needs.