CONFIDENTIAL PROJECT · MARKETPLACE + TELEPHONY

Expert consulting marketplace & Asterisk telephony ops

A two-sided paid consultation marketplace (client name omitted): the public portal helps callers discover experts by channel (phone, chat, email, SMS, premium-rate), register and top up prepaid credit; the VPS admin runs live calls over Asterisk AMI, wallets, payouts, call-center tools and CMS — one Laravel codebase with multilingual UX.

Laravel 4.2Asterisk AMIMarketplaceWalletsCall centerCMS
Industry
Paid consultation · telephony marketplace
Product
Public discovery + client/expert portals + VPS back-office
Roles
Client · consultant (Berater) · call-center agent · administrator
Stack
Laravel 4.2 · MySQL · Blade · Bootstrap 3 · jQuery · AMI HTTP
Proof
14 screens · three dashboard surfaces (client, expert, admin)

The problem

Operators selling minute-based phone, chat and email consulting cannot split work across a brochure site, a spreadsheet for wallets, a standalone PBX and a CMS. Clients need channel filters, tariffs by caller country, and credit before a live connect. Consultants need payout-ready onboarding (IBAN, tax data, consulting number) and presence that drives search ranking. Staff need live KPIs, Quick-Connect originate, and inventories of calls, chat and mail consults in one German ops console.

Constraints

Delivery stayed inside the client's stack, tenancy, compliance and media-ownership boundaries. Where a choice was forced (suite vs owned plane, BYOC vs CPaaS, local vs cloud models), the architecture section below records the trade-off rather than a marketing rewrite.

The solution

One Laravel application with custom role auth (ask_expert guard): guests browse and register; clients keep wallet, phones and callbacks while still filtering consultants; experts manage online status, callbacks, prices and billings; administrators use /admin for AMI-backed telephony, payments, payouts, Asterisk assets (prompts, MOH, voicemail) and content. Money, call state and CMS pages stay in MySQL; conferences charge through domain services aligned with Asterisk hangup.

Architecture

flowchart TB
  subgraph public [Public portal]
    Disc[Channel filters and tariffs]
    Reg[Client and expert registration]
    Login[Shared portal login]
  end
  subgraph portals [Logged-in portals]
    Client["Client dashboard"]
    Expert["Berater dashboard"]
  end
  subgraph vpsAdmin [VPS admin]
    KPI[Live calls and minutes]
    QC[Quick-Connect]
    Ops[Payments payouts CMS]
  end
  API[Laravel 4.2 app]
  DB[(MySQL)]
  AST[Asterisk AMI HTTP]
  Disc --> API
  Reg --> API
  Login --> Client
  Login --> Expert
  Client --> API
  Expert --> API
  Ops --> API
  KPI --> API
  API --> DB
  API --> AST

Public marketplace

Home lists consultants with filters: Alle, Gratisberater, Chat, E-Mail, SMS, 0900. Portal login, client and expert registration, magazine/help links, and a country tariff matrix (landline vs mobile surcharge) set expectations before credit is spent.

public portal with portal login channel filters and country tariff matrix

Registration (KYC-style onboarding)

Client signup captures identity, phone, credentials and AGB consent. Expert signup adds full address, consulting phone, IBAN/BIC and tax fields so payouts and telephony identity are captured once.

client registration with phone and legal consent checkboxes
expert registration with bank details IBAN BIC and tax number

Client & expert dashboards

After shared sign-in, groups split demand and supply. The client dashboard keeps marketplace filters with account chrome: wallet balance, free minutes, phones for callback CLI, callbacks, favorites, consultations, top-up (PayPal / Sofort / Paysafecard) and messages. The expert dashboard surfaces presence (online/pause/busy), open callbacks, recent activity, statistics and profile tools — PIN plus DDI for Asterisk consultant login.

Client (demand side)

client dashboard with wallet credit consultant filters and account sidebar
client account Stammdaten with dashboard navigation tabs

Expert (supply side)

expert dashboard with callbacks activity stats and consultant navigation
expert account with address PIN and credentials for telephony login

VPS admin & telephony ops

Separate admin login opens the operations floor: live-call and online-consultant tiles, calls and minutes today, Quick-Connect (pick consultant + client → originate), credit and free-minute grants, plus full German nav for transactions, payouts, call/chat/mail inventories, users, Asterisk voice prompts, music on hold, voicemail and CMS.

VPS admin login separate from public portal
admin dashboard KPI tiles Quick-Connect and operations navigation
admin user management searchable ledger with activation
admin payments grid with transaction ID amount and bonus columns
admin music on hold library for Asterisk Wartemusik
admin voicemail Sprachbox inbox
admin CMS hierarchical content pages privacy terms contact

Technology stack

PHP 5.6Laravel 4.2MySQLBladeBootstrap 3PayPal · Sofort · PaysafecardAMI HTTP /mxml

Legacy stack documented as delivered — modern rebuilds would use supported PHP, API-first clients and hardened AMI access.

What the screenshots prove

  • Three dashboards — same auth stack, different jobs (shop + wallet vs supply + presence vs ops floor).
  • Telephony in the product — not a plugin: admin KPIs, Quick-Connect, MOH and voicemail management.
  • Money in the loop — payment ledger, wallet top-up paths, consultant payout onboarding at registration.

Outcomes

The operator can run a paid consulting floor from a browser: discover consultants by channel, fund clients, originate and monitor Asterisk conferences, settle experts, and publish CMS — without splitting PBX, billing and marketing across tools. Screenshots are from a restored local instance; no invented conversion metrics.

FAQ — buyer & architecture questions

Ten common questions about this case study, fit, and engagement.

Two-sided consulting marketplaces with wallets, Asterisk AMI and admin ops—not only catalog browsing.

Clients top up; consultants onboard IBAN/tax data; admin reconciles payments and telephony usage.

No. Portfolio documentation only; production ran on the operator domain.

It orchestrates human consulting and PBX conferences; CPaaS may still carry SMS or overflow.

This page documents what was delivered; greenfield rebuilds use supported PHP and API-first clients.

Operators selling expert minutes, psychic/advice lines, or premium-rate consults with ops dashboards.

Share the current stack (PBX, CRM, cloud), the failure or goal in one paragraph, peak call volume, carriers, and any deadline. Screenshots, a pcap, or a short Loom beat a 40-page RFP. Use the project brief or email hello@unifiedpbx.in.

Yes. Delivery is remote-first from Delhi with scheduled overlap for EU, UK, US and APAC stand-ups. Production changes use written runbooks, rollback steps and agreed maintenance windows.

Yes. Many engagements begin with a 1–2 week SIP trace review, tenant-isolation audit, or architecture assessment. If the fit is good, scope expands from evidence—not from a generic sales deck.

Founders, CTOs, telecom leads, MSPs and product teams building or fixing UCaaS, CCaaS, CRM+voice, AI voice, or vertical SaaS—not buyers who only need seats on a mass-market suite.