I’m a client
Get support
Send a request or check on one. It gets a ref at once, then a person or an agent picks it up.
Brandcore Operations network
BCIO.NET
The operations network behind Brandcore.
If you work with us, this is where you get help.
Where to go
I’m on the team
Sign in
Desk, CRM and KB share one sign-in. Chat keeps its own.
Just curious
The studio
We design, build and run fast, static-first websites. The work lives at brandcore.io.
How a request moves
From hello
to done.
Four ways in, one route. Every message is filed, routed, answered and closed, and you hear from us when it lands and every time we answer. Pick where a message starts and follow it.
Example request. Real route: the statuses, events and emails are the ones the system uses.
Where it starts
Arrives
Status here: No status yetAn email to our support inbox. Replies find their ticket by the ref in the subject.
Logged as
email.receivedWhat you hear: Nothing to do yet.
Filed
Status here: NewA ticket with a ref you can quote, like BC-1042, and a card in the team's help channel.
Logged as
ticket.created#helpWhat you hear: A confirmation with your ref.
Routed
Status here: NewA person or an agent takes it: by rule (account owner, specialist, whoever's next) or by hand from the queue.
Logged as
ticket.assignedWhat you hear: No email. The support site shows who's on it.
Answered
Status here: In progressA person or an agent replies. Internal notes stay internal. Stuck agents hand off to a human.
Logged as
ticket.message_createdWhat you hear: Every reply, by email. Answer from your inbox.
Closed
Status here: DoneMarked Done. Reply to the last email and it opens again.
Logged as
ticket.status_changedWhat you hear: A note that it's done.
Leave a message
Write
to us.
About the studio, a project, or this page. It takes the website-form route above: filed as a lead, read by a person, answered within one business day.
Already a client? The support site is quicker: it gives you a ticket ref you can follow.