Openfair / Marketplace operations
Openfair: connecting calls, payments and client records
Aircall, Stripe, HubSpot and Slack held different parts of the client record. We connected the events to the people handling the next step.
A software delivery case, not a factory automation installation.
Delivered softwareThe problem
Client context was spread across calls, payments, records, and chat. Account managers had to rebuild the story before acting.
The key decision
Keep the team's existing tools, then route the relevant context into the place where the team already coordinates work.
What we built
Make the work clearer and easier to hand off.
- Call transcripts classified and attached to the correct HubSpot contact or deal
- Stripe payment success and failure signals routed to the responsible people
- Account manager support that keeps client context close to the daily workflow
- Lead classification that helps people see where attention is needed
Before the project
- Call, payment, and client context lived in separate systems.
- Account managers reconstructed the client story before acting.
- The next owner and next action could remain implicit.
Four tools, one client
An account manager at Openfair could find a call in Aircall, a payment in Stripe, the client record in HubSpot and the follow-up discussion in Slack. The information existed. Bringing it together was another piece of work before the person could decide what to do.
This project connected those events to the client context. A call transcript could be classified and attached to the right contact or deal. A payment success or failure could reach the person handling that client.
The place where the team already worked
A separate operating interface was considered. It would have given the team another place to look and another application to learn. Quindart chose to connect the existing tools and bring attention to the relevant person through Slack.
Aircall and Stripe remained the sources for calls and payments. HubSpot held the client context. Slack helped the team coordinate the next action. The important design decision was where that action would land.
What the connection carries
An event needs enough context to be useful. A payment failure on its own leaves the recipient with questions: which client, which record, and who is already handling it? The integration keeps those relationships close to the event.
The resulting workflow connects the systems the team uses. The person receiving an event can follow it back to the client record and the work already attached to it.
The working process
- A website inquiry, call, or payment event arrives
- Relevant context is attached to the client record
- The operating record is updated with the current signal
- Slack directs the responsible person to the next action
What changed
- Payment and call events are harder to miss
- Account managers can act without rebuilding the story from separate tools
- New staff learn one operating route instead of a collection of disconnected systems
Systems involved
Aircall · HubSpot · Stripe · Slack
Your workflow