AI Marketplace Operations Administrator · Australia

The sellers keep coming. The desk keeps up.

Bryn assembles and chases seller onboarding packs, checks listings against your own rules, triages merchant and buyer enquiries with reply drafts, and logs refund and dispute requests for a person to decide. A named human approves every seller, listing, message and payment.

  • Human approval
  • Seller and refund decisions stay human
  • Records in your systems
WORKER / SF/26 AVAILABLE FOR AUDIT
Marketplace operations administrator

Bryn

The platform desk for the founder who approves every seller and every refund.

ON BRYN'S SHIFT
MON

Refresh the seller onboarding register and chase missing items

CHECK
TUE

Check new and changed listings against your rules

APPROVE
THU

Triage enquiries and draft replies from your templates

APPROVE
FRI

Hand off refund and dispute requests and the exceptions report

HANDOFF
MODE HUMAN APPROVALSAFETY ESCALATE

[ THE PLATFORM DESK ]

Every seller, listing and request on a register with an owner.

At the end of each week, every seller in onboarding has a stage and a dated chase, every new listing has passed or been flagged, every enquiry has a drafted reply awaiting approval, and every refund or dispute request has an owner and a deadline.

01

Seller onboarding

Assemble each seller's onboarding pack from your checklist, name what is missing and chase it on the agreed cadence.

02

Listing checks

Check new and changed listings against the rules you have written: required fields, pricing format, images, categories and restricted statements.

03

Enquiry triage

Sort merchant and buyer enquiries by type and urgency and draft the reply from your templates and the record.

04

Refund and dispute log

Log each request with the order, the evidence received, the deadline and the next step for a person to decide.

05

Catalogue hygiene

Flag stale, duplicate and incomplete listings and lapsed seller details for review.

06

Weekly exceptions

Compile the onboarding, listing, enquiry and refund exceptions report with ages and owners.

Excluded work: approving or declining a seller, publishing or removing a listing, deciding a refund, dispute or payout, any health, treatment or qualification judgement, any payment, and any autonomous message to a buyer or seller. These stay with your named people.

[ START WITH ONE WORKFLOW ]

Choose the register to keep current.

Read access to your seller application forms, listing exports, the shared support inbox and your written marketplace rules is mapped at onboarding. A spreadsheet and inbox workflow also works.

WORKFLOW / 01SELLER ONBOARDING

Pack and chase

Keep each applicant's pack status current and chase missing items until a person can decide.

START
Applications and your onboarding checklist
DONE
Pack complete or chased with a dated gap
HUMAN
Approves or declines each seller
WORKFLOW / 02LISTINGS

Rule checks

Check every new and changed listing against your rules and flag each failure with the rule it breaks.

START
Listing exports and your written rules
DONE
Each listing passed or flagged
HUMAN
Publishes, edits or removes
WORKFLOW / 03SUPPORT DESK

Enquiries and refund requests

Triage the inbox, draft replies, and log refund and dispute requests with evidence and deadlines.

START
Shared inbox and order records
DONE
Reply drafted or request logged with an owner
HUMAN
Approves each send and decides each refund

[ THE APPROVAL LANES ]

What Bryn does.
What your team decides.

Internal register and drafting work runs within the agreed scope. Anything a buyer or seller would see waits for a named human. Seller, listing, refund and payment decisions remain with your people.

GREEN

DOES-IT-ALONE

Internal registers and drafts within the agreed workflow.

  • Assemble seller onboarding packs from your checklist and name every missing item
  • Check new and changed listings against your written rules and flag each failure
  • Triage enquiries and draft replies from your templates and the record
  • Log refund and dispute requests with evidence, deadline and next step
  • Compile the weekly onboarding, listing, enquiry and refund exceptions report
AMBER

APPROVE

A named human approves before release or external contact.

  • Send any message to a seller, buyer or applicant
  • Mark a seller pack as complete and ready for decision
  • Change any rule, template, checklist or register structure
  • Escalate a listing or request outside the standard queue
RED

NEVER

Outside Bryn's authority.

  • Approve, decline, suspend or remove a seller
  • Publish, edit or take down a listing
  • Decide a refund, dispute, chargeback or payout, or move any money
  • Judge whether a health, treatment or qualification statement is allowed
  • Give legal, regulatory, consumer-law or tax advice
  • Send any message, make any commitment or write to any system without a named human's approval

[ MINIMUM ACCESS ]

Your seller and buyer records stay yours.

Registers live in your systems or a client-owned sheet. Bryn keeps no copy of buyer or seller personal details beyond the engagement. Access begins read-only; a register write requires your express grant.

The load audit uses a blank register, redacted applications and your written rules. Live data access and retention are mapped during onboarding.

  1. 01

    Map inputs

    Identify application forms, listing exports, the support inbox and your written rules.

  2. 02

    Set access

    Use read access first; grant a register write only if the approved workflow needs it.

  3. 03

    Test fictional cases

    Test an incomplete seller pack, a listing with a restricted statement, a refund request and a complaint.

  4. 04

    Name approvers

    Name who approves sellers, who publishes listings, who approves messages and who decides refunds.

[ OPERATING SPECIFICATION ]

Proposed turnaround.
Confirmed at onboarding.

Proposed timings are a next-business-morning register entry for new applications and requests, listing checks within one business day of submission, reply drafts within the same business day, and a weekly report on a fixed day. The delivery team confirms these against your volume during onboarding.

Example output — fictional seller A
Pack complete; ready for your decision
Example output — fictional seller B
Insurance certificate missing; second chase sent after approval
Example output — fictional listing C
Restricted treatment statement; flagged to named person
Example output — fictional request D
Refund request logged with evidence; decision due in two days
Weekly measures
Sellers in onboarding by stage and age; listings passed and flagged
Weekly measures
Enquiries awaiting approval; open refund and dispute requests by deadline
CONTROL / 01ONBOARDING

Start with the written rules

Set up read access, load your onboarding checklist and listing rules, back-fill the current applicant and listing queue and review the first report with your approver.

CONTROL / 02CAPACITY

Size the seat to the work

The delivery team confirms a range of applications, listings and enquiries per week per seat. Beyond it, narrow the scope or add a seat.

CONTROL / 03ESCALATION

Surface exceptions to a person

Escalate after the agreed chase count, for any restricted statement, for any request near its deadline and for any complaint that reads as legal or regulatory.

CONTROL / 04SAFETY

Immediate human handoff

Any message that appears to involve harm, a safety incident or a vulnerable person goes straight to your named person, outside the standard queue.

Capacity and turnaround are confirmed during onboarding for your application volume, listing count, enquiry volume and reporting day.

[ MARKETPLACE LOAD AUDIT ]

Map the platform desk.

Bring redacted applications, a listing export and your written rules to choose one bounded workflow and its human approvals.

Book the Marketplace Load Audit Access is agreed before live work.

[ FROM AUDIT TO TRACKED WORK ]

One workflow.
Named approvers.

STEP 1

Load audit

Review redacted records and choose the first workflow.

STEP 2

Map access

Confirm sources, rules, retention and register permissions.

STEP 3

Test fictional cases

Check an incomplete pack, a flagged listing, a refund request and a complaint handoff.

STEP 4

Review the first report

Your approver checks the report, cadence and escalation route.

[ BEFORE THE AUDIT ]

Questions about the platform desk.

Does Bryn approve new sellers?

No. Bryn assembles the onboarding pack, names what is missing and chases it. Your named person approves or declines each seller.

Can Bryn publish or take down a listing?

No. Bryn checks each listing against the rules you have written and flags what fails. A named human publishes, edits or removes it.

Does Bryn decide refunds and disputes?

No. Bryn logs each request with the evidence received and the deadline, drafts the holding reply, and hands the decision to your named person. Nothing is refunded or charged by Bryn.

Does Bryn reply to buyers and sellers?

Bryn drafts the reply from your templates and the record. A named human approves every outbound message before it sends.

What about health, treatment or professional claims in a listing?

Bryn flags any listing that makes a health, treatment or qualification statement your rules restrict and routes it to your named person. Deciding whether it is allowed stays human.

How is Bryn different from your dental clinic worker?

Maya runs one clinic's own front desk. Bryn runs the marketplace's desk: the sellers, listings, enquiries and refund requests across every business on the platform.

Can Bryn also work for the businesses on our marketplace?

Not from this seat. Each business on your platform is its own engagement with its own approver. Bryn covers the platform's operations only.

Do we need a marketplace platform or admin tool in place?

No. Bryn can work from a shared inbox, form exports, a listing spreadsheet and your written rules. Access and any register write are agreed during onboarding.

What appears in the weekly report?

Sellers in onboarding by stage and age, listings checked, passed and flagged, enquiries triaged and awaiting reply approval, and open refund and dispute requests by age and deadline.

When does something escalate to a person?

A seller pack still incomplete after the agreed chase count, a listing with a restricted statement, a refund or dispute near its deadline, any safety or harm concern, and any message that appears to be a legal or regulatory complaint go straight to your named person.

[ START WITH YOUR OWN QUEUE ]

Grow the marketplace. Keep the desk current.

Map seller onboarding, listing checks, enquiries and refund requests with each approval assigned to a person.

Book the Marketplace Load Audit Direct with the founder