ACTIVITY
Checkout activity
SuccessfulRejected
—
YOUR BOT NETWORK
Operations overview
A clear view of checkouts, rejects and order records across your team.
NEEDS ATTENTION
Top rejection reasons
FIVE BOT SOURCES
Bot performance
LATEST SIGNALS
Recent activity
WHERE ACTIVITY HAPPENS
Retailer snapshot
ALL BOT ACTIVITY
Checkout events
Search purchases, rejects and bot messages from the full team. Open an event to validate AI field suggestions before applying them.
| EVENT | PRODUCT / RETAILER | PROFILE | BOT | RESULT | DISCORD | WHEN |
|---|
ORDER RECORDS
Order mail
Review imported messages and link them to successful checkout events.
Recent messages
Suggestions rank possible checkouts by matching clues; review before linking. Not relevant mail can be restored any time.
| MESSAGE | TYPE | ORDER | MATCHED CHECKOUT / REVIEW | ATTACHMENTS | RECEIVED |
|---|
PROFILE ATTRIBUTION
Team profiles
Register teammates once. Profile names are matched automatically, so you do not need an alias row for every profile.
TEAM ROSTER
Add a teammate
Add each team member once. Flips AIO first checks for their name in profile strings, then uses AI for unclear matches against this roster.
TEAM SIGNALS
Attribution summary
These counts come from webhook profiles and their assigned teammate, not from the Order mail page.
Registered teammates
Removing a teammate also clears their explicit profile overrides and recalculates unassigned profiles.
| TEAM MEMBER | ADDED |
|---|
Optional exact profile overrides
Use only when a profile name does not make its teammate clear. This is an exception list, not a required row for each profile.
| PROFILE OVERRIDE | TEAM MEMBER | ADDED |
|---|
CONNECTIONS & ROUTING
Integrations
Route each bot event through Flips AIO and keep the original Discord posts flowing.
How the relay worksReplace each bot's Discord webhook URL with the matching Flips AIO URL below. Flips AIO stores the event, then forwards the original JSON to the Discord destination configured for that bot and outcome.
SMART ROUTING
AI outcome sorting
Enable this for bots that send success, rejection and info notifications to one webhook URL. AI classifies each captured message before it is forwarded.
Single-webhook botsWhen enabled, choose one receiver URL for that bot and use it for all its notifications. The bot in the URL still identifies the source; AI selects success, reject or info. If AI is unavailable or unsure, the URL's outcome is used.
| BOT | SMART OUTCOME DECISION | ENABLED |
|---|
INBOUND ROUTES
Bot webhook URLs
Use separate URLs for separate event types, or use one URL and enable AI outcome sorting above. Set a fallback outcome for each URL; it applies when AI sorting is off or unavailable.
| BOT | URL TYPE | FALLBACK / MAPPED STATUS | FLIPS AIO RECEIVER | CONTROLS |
|---|
DIAGNOSTICS
Developer mode
When enabled, webhook event details display the complete incoming JSON directly above the mapped fields. Open or reopen an event to load it.
Raw data warningWebhook bodies can contain profile names, email addresses, order details, proxy credentials or payment metadata. Raw data is only returned to the authenticated dashboard while this setting is on.
AI ANALYSIS
Provider status
Claude runs first when configured. OpenAI is used automatically if Claude is unavailable or returns an error.
MAILBOX
Email ingestion
Create a mail rule to forward order confirmations and invoices to the mailbox shown in your environment settings. Flips AIO reads it over IMAP.