Reference
Answers to common questions about Tap Agent approvals, media support, MCP access, Plans, RFPs, Avails, Orders, Deals, and permissions.
4 min readUpdated
Something missing from this page? Email help@tap.co
Tap can help structure a Plan from campaign intent and assist with research or drafting. The buyer remains responsible for campaign direction and approvals.
No. The buyer reviews the exact request and recipient list, then explicitly approves the named send action before a supplier is contacted. This applies to broadcast and DOOH RFPs.
No. AI may organize and compare submitted Avails or inventory options, but a person decides which response advances to an Order or another commercial step.
No. RFP Exchange conversations, Avail Responses, Orders, supplier Deals, and DOOH responses preserve the direct relationship and context between buyer and supplier.
No. Buyers and suppliers remain responsible for their own media agreement, credit, invoicing, and payment. Tap invoices only for its own approved fees, subject to the current terms.
Yes. Tap exposes an authenticated buyer MCP server at https://mcp.tap.co. A compatible AI client can connect to the buyer organization selected during sign-in and use the published buyer command catalog. Read Connect Tap to an AI client before connecting a client, especially the sections on organization selection, approval, privacy, and reconnection.
This public Tap server is different from the Custom MCP server option inside the Tap Agent. The public server lets another AI client operate Tap. The Custom MCP option lets the Tap Agent use one remote server you configure.
Tap currently supports in-product transaction paths for radio, TV, and digital out-of-home. DOOH supports inventory discovery, Plan allocation, directional estimation, RFP drafting, buyer-approved sending, and a supplier response. The Tap Agent may recommend other media as planning advice, but the corresponding transaction happens outside Tap until an in-product path is available.
A sent revision does not change silently. Editing a material detail stages a new revision while suppliers keep seeing the previously sent copy until you review and explicitly resend it.
No. Changing only the deadline is a separate amendment. Approving the new deadline updates the open RFP Exchanges without creating a new material RFP revision.
You can permanently delete an unsent draft Plan after reviewing the warning. Sent RFPs and Orders cannot be removed through that cleanup action. Archive a Plan when you need it out of the active view without destroying transaction history.
If the RFP Exchange is still open, Tap can accept the Avail Response and label it late. If the Exchange has closed, it remains visible as a record but no longer accepts changes or new Avails.
Tap rechecks selected Avails before an Order is placed. Withdrawn, expired, superseded, closed, or stale Avails cannot be added to a new Order.
Yes, while it is waiting for the supplier decision. Once the supplier confirms or declines, that decision is final for that Order.
It means the supplier offered a different fit from the exact request. Review the supplier reason before treating the option as equivalent.
No. A Deal starts with the supplier. It can be public to eligible buyers or delivered directly to selected contacts. A buyer can respond, request a private quote, message the supplier, and order available lines while the terms remain open.
Creating or editing a Deal requires Edit Deals. Ask a teammate with Manage team permissions to grant access, or ask a teammate with Edit Deals for that property to create it.
Full Pipeline visibility requires View pipeline at the organization, market, or property scope. Without it, a person generally sees work assigned to them or work they created.
If no routing rule matches and the default receiver group is empty, grant Receive RFPs to at least one teammate for that property. Routing assigns work only to eligible receivers; it does not create access.