View all app connections
View all AI automations
View all chatbots
View all lead automations
View all booking automations
View all payment automations
View all workflows
View all Shopify
View all WooCommerce
View all HubSpot
View all Salesforce
View all Stripe
View all Google Sheets
View all Slack
View all dental practice
View all law firm
View all medical practice
View all real estate
View all restaurant and food
View all home services
View all construction
See all: get more leads
See all: get paid faster
See all: save admin time
See all: support customers
See all: book more appointments
See all: sell more online
See all: hire and onboard
View all AI automations
View all AI automations
View all AI automations
View all AI automations
View all AI automations
View all AI automations
View all AI automations

BoldBellowsA decision, not a notification

Turn a high-value eBay return into a real Teams decision, not a ping

A plain webhook message tells someone that a return exists and leaves them to dig up the order on their own. This build posts an Adaptive Card carrying the actual evidence — order detail, refund amount, case history — with approve, investigate and decline built right into the card, and nothing touches eBay until a named reviewer makes that call.

View Pricing

From $450, paid once.
No monthly connector fee.

  • Real order evidence, not a bare notification
  • Nothing touches eBay before a person decides
  • A working decision card, ready to review within two weeks
eBay to Microsoft Teams automation by BoldBellows: a return decision card posted to Teams with real order evidence, capturing approve, investigate or decline before any action ever reaches eBay
Decision recorded Action followed approval CARDS · THIS WEEK Decision cards posted21 Stale refunds re-flagged3 Actions taken without approval0 Every card traces to a real case

What a case has to clear before a card ever posts

  • Only cases crossing the review threshold get a cardnever a card for every return
  • Case ID, order ID and decision revision travel togethernever a subject line someone has to interpret
  • A changed refund amount pauses the card againnever lets a stale decision go through
  • A card shows only what a reviewer needs to decidenothing extra from the order payload
  • The quote you agree to is the quote you payno surprise line item once cards start posting

01The skim-past trap

A notification isn't a decision

A plain webhook message says a return happened and stops there, leaving whoever reads it to open eBay, find the order, and figure out what to do next on their own time. By the time that happens, a genuinely urgent case has already sat unresolved for hours.

"A high-value refund request sat in the channel for two days before anyone acted."

The message existed, but nothing about it made the case feel urgent enough to open right away.

"Someone approved a refund, then the buyer changed the amount an hour later."

The approval had already gone out against a number that was no longer accurate by the time it landed.

"Nobody could say who had actually approved a decision after the fact."

A plain text message left no record of who decided what, or when.

A message someone has to act on manually isn't automation, it's a to-do list dressed up as a notification. The decision has to live in the same place as the evidence.

Same return cases, same eBay account. The difference is whether Teams shows a decision waiting to be made, or a message waiting to be interpreted.

Before

Teams channel · plain text Evidence: not included Decision: made somewhere else
  • Nobody sees the actual order evidence
  • A stale refund amount can slip through
  • No record of who decided or when

After

Decision card · case RC-4471 Order 88214, refund $340 ✓ Real order evidence shown on the card ✓ Approve, investigate, decline built in ○ A changed refund pauses it again
  • Real order evidence right on the card
  • A stale refund never slips through
  • Every decision has a name and a time

02How it works

How a return case becomes a Teams decision card

The case gets read against the review threshold first, its identity gets claimed as the card's reference second, the Adaptive Card gets built and posted third, and only a recorded decision ever authorizes an action back on eBay.

A changed refund re-pauses the card here STEP 1Case read Checked against thereview threshold STEP 2Identity claimed Case, order and revisionmatched together STEP 3Card posted With evidence andthe three decision options STEP 4Decision proven Only once a personactually chose STEP 1Case read Against the threshold STEP 2Identity claimed Case and order matched STEP 3Card posted Evidence plus 3 options STEP 4Decision proven Only once chosen A changed refund re-pauses it here
Nothing gets actioned here on its own. The card waits exactly as long as it takes a real person to look at real evidence.

Why the card has to carry evidence, not just a link

  • A Teams workflow can receive a webhook and post a structured Adaptive Card in response. That's the exact mechanism that lets a decision live in the same place as the evidence, instead of in a separate tab.
  • A shipping fulfillment doesn't count as settled until its result is confirmed, never just assumed from a status code. A card follows that identical discipline before treating any decision as final.
  • eBay itself never conflates a SKU with the offer or the listing built on top of it. A card inherits that same precision when it points a reviewer at the exact item a return concerns.

03Package by package

How the card program grows from Foundation to Assurance

Foundation gets a real decision card posting for every qualifying case. Control adds the branch that catches a refund changing after the card is already open. Assurance puts a standing sweep behind both of them, so a case the live feed missed still surfaces on its own schedule instead of waiting to be noticed.

Decision Card FoundationDecision Card ControlDecision Card Assurance

Card log CaseRefundReviewerStatus RC-4401$120PriyaApproved RC-4406$85PriyaDeclined RC-4409$210MarcoInvestigating RC-4471$340 → $260MarcoRe-flagged RC-4471Amount changedMarcoHeld Refund changed → card re-flagged, not approved eBay ReadClaimedPostedDecided Card log CaseStatus RC-4401Approved RC-4409Investigating RC-4471Re-flagged RC-4471Held Refund changed → re-flagged eBay Read+ 3 more views

Human-review threshold filter Decision Card Foundation

Reads only the cases that genuinely need a person's call, and records why.

Case-and-order identity claim Decision Card Foundation

Anchors every card to the exact case and order it represents.

Stale-card revalidation branching Decision Card Control

Catches a refund changing mid-review and re-flags the card instead of trusting it.

Owned exception register Decision Card Control

Turns a re-flagged case into a task with a named owner.

Scheduled reconciliation Decision Card Assurance

Sweeps eBay's own case data on a standing schedule, catching what a single missed webhook never would.

Contract drift detection Decision Card Assurance

Notices when eBay or Teams quietly redefines a field, before a card starts showing stale data.

Decision-history and action-queue handling Decision Card Control

Keeps a record of every decision, with the reviewer's name attached.

Thirty-day launch review Decision Card Assurance

A full production month of real decisions runs before we call it complete.

PROGRAM HEALTH Decisions recorded, this month Actions taken without approval Open count 0
Decision Card Assurance adds this view — decisions recorded climbing steadily while unapproved actions hold flat at zero.

04Who it's for

Built for teams that want a real approval, not a ping

Built for a marketplace ops lead who wants a name attached to every high-value call, a seller team burned once by an outdated refund number, a department approver who'd rather read evidence than chase a link, and an admin who needs a re-flagged case landing on a specific person's desk.

Marketplace operations lead

Wants proof a high-value case was actually decided by a person, not silently auto-approved.

Seller team

Tired of a refund amount changing after approval and nobody catching it before the money moved.

Department approver

Wants the actual order evidence right on the card, not a link they have to chase down separately.

Systems administrator

Wants a re-flagged case routed to a specific name, not left sitting in a channel nobody's watching.

05Compare

Where a plain webhook message actually breaks down

Posting a plain text alert to a Teams channel takes minutes to wire up. Carrying real order evidence into the decision, and catching a refund that changes after someone's already looking at the card, is where that shortcut runs out of road.

A side-by-side of a plain webhook message, a one-step Power Automate flow, and the BoldBellows decision card build
What actually mattersPlain webhook messageA one-step Power Automate flowBoldBellows build
What starts a cardAny return event, unfilteredA single trigger, firing on whichever event tripped itYesA case crossing the review threshold, specifically
How it's matchedA subject line, read by eyeWhatever field the trigger exposesYesCase ID, order ID and decision revision together
What Teams getsPlain text, no way to actThe same flat message card, regardless of what the case actually needsYesAn Adaptive Card with evidence and decision options
When the refund changesNobody notices at allOutside what a single trigger step was ever designed to watch forYesRe-flagged before any decision counts

The stale-decision trap

A refund amount changes after a reviewer has already opened the card. Stale-card revalidation branching catches the mismatch and re-flags the case instead of letting an outdated approval go through.

The unconfirmed-post trap

A card gets sent to Teams but nothing confirms it actually posted. Reconciliation checks the case-and-order pairing before anything retries, so a resend updates instead of duplicating.

PricingClear, one-off packages

Give Teams a real decision, not another ping

The three packages differ by how much stale-card handling and self-checking the program carries — tick a box on the left and watch the right-hand card reprice as your choices land. Decision Card Foundation opens at $450.

View Pricing
Pricing

Build your eBay to Microsoft Teams price

Pick a package, answer three short questions about event scope, identity and failure policy, and your price and turnaround move as you choose.


Choose your packageRequired

The three packages differ by how much branching and recovery depth the card handles.

One eBay account and one Teams channel, posting a decision card for a qualifying case from day one.

  • One authorized eBay account, one Teams channel
  • Human-review threshold event filter
  • Case-and-order identity claim
  • Duplicate-card replay defense
  • Standard and duplicate-path acceptance tests
  • Focused administrator handoff

Handles a refund amount that changes after a card is already open, with an owned exception state.

  • Everything in Decision Card Foundation
  • Stale-card revalidation branching
  • One historical reconciliation pass
  • Owned exception register
  • Decision-history and action-queue handling
  • Mapping change notes

Scheduled reconciliation and drift detection keep the whole decision-card program honest at volume.

  • Everything in Decision Card Control
  • Scheduled eBay-state reconciliation
  • Contract drift detection
  • Operational evidence register
  • Volume and timeout protection
  • Thirty-day launch review

Several eBay accounts, regulated retention, custom extensions or unsupported add-ons. Tell us the real scope and we will price it for your build.

Which cases should actually post a decision card?Required

Lifecycle with reconciliation adds a sweep that catches a change the live feed missed.

How should a card trace back to its eBay case?Required

Conflict quarantine adds a queue for a match the rule can't confidently resolve on its own.

What happens when a Teams post fails?Required

Creating an operator case takes more setup than a stop, but nothing silently falls through.

How soon do you need it live?Required

Standard follows the schedule your other choices set. Pay to move up the queue and go live sooner.

Optional extrasOptional

Each one begins switched off. Turn on what your rollout needs, watch the total, switch it back off.

06The process

Proving a card holds up before it reaches a reviewer

Decision Card Foundation needs one eBay account and one Teams channel, and most teams have a real card to review inside a week or two. Control takes longer because we deliberately change a refund amount right after a card has already been opened, and repeat that exact timing until the revalidation branch catches it every single time. Assurance spends its extra days on a different exercise: we let a field go stale on one side and confirm the standing sweep surfaces it on its own, with nobody having to eyeball the numbers to spot the drift. If a busy season usually means a spike in returns for you, mention it early so we can size the rollout around that volume rather than around an average week.

Your decision-card worksheet What actually crosses the review threshold Which channel and reviewers should see a card Who owns a re-flagged case when it opens How far back a historical backfill should reach Built from how your team actually reviews cases Build summary Test set: 18 cases run Cards posted 18 Stale refunds caught 4 Unapproved actions 0 Ready for handoff
  1. Define what genuinely needs a decision

    We go through your recent return cases with you and agree on the line between routine and genuinely high-value.

  2. Design the card and the routing

    You approve what evidence appears on the card, who sees it, and exactly what a re-flagged case should trigger.

  3. Build the decision engine

    The threshold filter, the identity claim and the revalidation logic all get assembled around your real Teams channel.

  4. Try to slip a stale decision through

    We change a refund right after opening a card and watch whether the system catches it, before we ever trust it with a real case.

  5. Go live, then step back

    A genuine case posts a real card, a real reviewer decides, and we confirm the result before your team takes over.

Three things to have ready

  • Approval from whoever has admin rights on your eBay account.
  • Someone who can create an incoming webhook on the target Teams channel.
  • A list of who should be authorized to approve, investigate or decline.

07Security and ownership

Reads a case to show it, never to act on it alone.

What this build touches on eBay stays limited to order and case detail, and what it does with that data is post a card into the single Teams channel you name. There is no path from it to a listing edit, a refund, or any channel you didn't authorize.

No power to act on eBay by itself

The build can read order data and post a card, but it holds no ability to issue a refund, cancel an order, or take any action without a recorded human decision first.

A fixed set of fields, shown on every card

Only the evidence fields you approve in advance ever appear on a card — nothing from the order payload beyond that list gets displayed.

Nothing that unlocks a write is on a card

Every credential this build holds sits in a vault a card never touches — no key, token or secret ever rides along in a card, a comment, or an attachment.

A retried post updates, it never duplicates

The case-and-order pairing is checked before a card ever goes out, so a repeated delivery finds and updates the same card instead of posting a second one.

The audit trail shows who decided what

What's retained is the reviewer's identity, the choice made and the timestamp — never a duplicate of sensitive order or payment data.

You keep the whole program at handoff

The threshold rules, the card design and a written runbook transfer to you outright — nothing about it stays dependent on us.

08In their words

What BoldBellows clients say

Verified reviews from teams who use BoldBellows automations every day, from marketplace operations to sales and customer follow-up.

AI CRM Automation

Our CRM was barely used because updating it by hand was tedious. BoldBellows automated data entry, tagging, segmentation and follow-ups.

Now the CRM is always up to date and our campaigns are far more accurate. It improved our whole sales pipeline.

David KimVerifiedSeoul, South Korea

AI Booking & Scheduling Automation

Our coaching business needed a better way to schedule. BoldBellows automated all of it: bookings, reminders, cancellations and follow-ups.

No-shows fell by 60% and clients enjoy how smooth it is. It feels personal, not robotic. One of the best upgrades we’ve made.

Emily CarterVerifiedLondon, United Kingdom

AI Lead Qualification & Sales Automation

Our sales team wasted hours chasing cold leads. BoldBellows built an AI lead-scoring system that reads behavior, email engagement and buying signals.

It filters out weak leads and sends personalized follow-ups automatically, so our team only talks to people who are ready to buy. Conversions rose 40% in the first month. It paid for itself straight away.

Aisha MohammedVerifiedDubai, UAE

AI E-commerce Listings Automation

BoldBellows automated our product listings. The AI writes descriptions, organizes photos and publishes listings across several marketplaces.

It even answers customer questions instantly. Our store looks more professional and sales have noticeably increased.

Pedro LimaVerifiedSão Paulo, Brazil

AI HR & Recruitment Automation

Our HR team was drowning in applications. BoldBellows automated screening, skills-based filtering and interview scheduling.

It saves us hours every week and means we only interview qualified people. Hiring is now faster, better organized and more professional.

Olivia MartinezVerifiedAustin, USA

AI Chatbot & Customer Support

BoldBellows built an AI support chatbot for our online boutique, and it has changed how we run the business. We used to have two full-time staff answering the same questions all day. Now the AI handles order tracking, product recommendations and even refund requests on its own.

What surprised me most is how natural it sounds. Customers compliment the ‘agent’ without realizing it’s AI. Our support workload dropped by 75% and customer satisfaction went up dramatically.

Maria GonzálezVerifiedMadrid, Spain

AI Document & Contract Automation

Onboarding was slow because we wrote every contract by hand. BoldBellows automated the lot: contracts, welcome emails and client setup.

What took 48 hours now takes under 10 minutes, and clients regularly tell us how professional it feels.

Michael O’ConnorVerifiedDublin, Ireland

AI Email & Smart Inbox Management

Our inbox used to be chaos. BoldBellows built an AI email system that sorts messages, drafts replies and flags anything urgent.

It learns how we write and gets better every week. We reply faster and no longer miss important messages. It feels like having a personal assistant working around the clock.

Chloe AndersonVerifiedMelbourne, Australia

AI Accounting & Invoice Automation

BoldBellows automated our whole invoicing process: creating invoices, sending reminders and tracking payments.

Late payments dropped sharply, and our accounting team finally has time for strategy instead of repetitive admin. Worth every penny.

Ravi PatelVerifiedNew Delhi, India

09FAQ

Questions worth asking before the first card posts

Still unsure? We reply in plain English.

We already post a Teams message when a return comes in. What does this add?

A plain message tells someone a return exists and stops there — it can't show the order evidence, capture a decision, or notice when the refund amount changes after someone's already looking. Turning the notification into an actual decision point is what this build does.

Can this take an action on eBay without someone approving it first?

No. The build can only read order data and post a card — it holds no permission to issue a refund or take any other action until a recorded decision authorizes it.

Can we pull older return cases into the system to build a decision history?

The historical case backfill covers that: pick a window of past cases, and it runs the same threshold logic against them and posts the cards they would have produced, entirely on its own track so nothing collides with a live case in progress.

Does our Microsoft 365 licensing factor into the price you're quoting?

No — this is a single build fee, paid once, for the decision-card program itself. Whatever you already pay for Microsoft 365 or for selling on eBay keeps running on its own separate billing.

Who finds out first if eBay or Teams breaks something this depends on?

You get a handoff document that spells out every field, endpoint and permission the program actually uses, so nothing about its dependencies is left to memory. And the drift check finds out first — it's built to flag a broken contract on its own, well before a card starts quietly showing numbers that no longer line up.

If Teams doesn't confirm a card posted, could the same case end up posting twice?

No. A retry looks up the case first, finds the card already tied to it, and edits that one in place — there's no path where the same case ends up with two separate cards sitting in the channel. If you searched for ebay to microsoft teams, ebay orders teams notification and ebay microsoft teams integration, this is the service that delivers it.

Next stepStop letting a return sit unread in a channel

Give Teams a decision your team can actually trust

Tell us which return cases your team is still digging up by hand and which Teams channel should carry the decision, and we'll turn that into a fixed number. Decision Card Foundation starts at $450.

  • From $450, paid once
  • Every decision carries a name and a timestamp
  • A changed refund gets re-flagged, not approved
  • You keep the whole decision-card program