Freebee Ads docs

Engineering docs

The Sales desk

Last updated Oct 20, 2018 · 5 sections

Where a Freebee sales person works. Pages under /ops/sales. API under /v1/ops/sales.

Who the sales person is

One person who brings a business from "hello" to a running ad, and back for a second booking. Our first customers are shops and restaurants inside the mall. They decide in a day, the owner decides, and most of them have no ad. Big brands are sold by hand, over weeks.

A sales person is not a clerk who types bookings. Their job is to remove whatever the customer is stuck on: no login, an email they never opened, no ad, an ad that was sent back, a price, an unpaid bill, a campaign that ended.

A good day. Open My day. Ring the three people whose follow-up is due. Walk the food court and add two new shops as prospects. Send one invite. Help one owner pick a ready ad. Chase one unpaid booking. Tell one restaurant how many coupons came to the counter last week, and ask about next month. Every call ends with a next step and a date, so nothing waits on memory.

The customer's path

Each step reads its state from the tables we already have. Nothing is typed twice.

#StepWhat the customer is stuck onWhat Sales doesWhat the desk shows
0ProspectDoes not know us yetVisit, call, note the shop, set a next stepName, kind, mall, where they came from, owner, next step
1Account madeWill not make a login, or cannotSend a sign-up invite to their email (they choose the password), or link the account they already madeInvite sent when, or the linked account
2Email confirmedNever opened the emailSend the link again, or confirm it by hand after a call (both are audited)Waiting since; when the last link went out
3Kind of business setWe never askedAsk, set it on the deskOne of the eight kinds
4Reason chosenDoes not know what to ask forAsk the one question: Remember me, Try me, Come now or Call meThe reason
5Ad readyHas no adCollect a picture and the offer, or use a ready-made adAds on file
6Ad approvedAd waiting, sent back or refusedShow the reason, help fix itWaiting since; the reviewer's reason
7BookedPrice, dates, screensPlace a hold, quote a price, book for themHolds, price talks, bookings
8PaidBill not paidChase; Finance or Sales marks paid with a referenceUnpaid since
9PlayingBooked but nothing plays yetCheck the ad is approved and the screen is upLive since; plays so far
10First results sharedNever saw the proofSend the results, record that it was doneWhen it was shared
11RenewedEnded, no next bookingTalk renewal a week before the endBookings count, end date

The current stage is the first step not done. "Stuck for" is the time since the step before it was done. A customer can also be closed: lost (never bought) or stopped (wanted to stop), with a reason. Closed customers leave My day and can be reopened.

"Make a plan for this customer" (step 7, and on the Campaigns card) opens /ops/sales/customers/[id]/plan (rt_plans_flow): the same plans engine as the customer's own booking, at their prices. Sales send the plan: the customer opens the link in their own login, picks or makes the ad and pays. Where the rules below allow booking on their behalf, Sales may book it for them from that page, only after an Agreed entry recorded after the plan was made; the booking is confirmed unpaid and the plan is kept with source = sales and the Sales person as its maker. A prospect with no account can have plans worked out and talked through, not sent. A sent link stops working after the quote validity (booking.quote_validity_hours); prices are always worked out again when it is opened.

Do it with them, not as them

Sales prepares; the customer agrees and pays.

  • Sales never logs in as the customer. There is no such button and there will not be one.
  • A sign-up invite lets the customer set their own password. Sales never sees or sets it.
  • A quote is accepted by the customer from their own login (existing price requests).
  • When the customer has no login or cannot use a computer, Sales books on their behalf with the existing paths (hold, then convert; or book on behalf). Before that, Sales records the customer's yes in the contact log as an Agreed entry (what they agreed to, how: in person, by message). The desk shows it on the booking step. Payment is still the customer's own: online, or in person and marked paid with a reference by Sales or Finance.
  • Every sales action writes to the audit trail: add, edit, claim, hand over, close, link, invite, resend, confirm by hand, record results shared, each note and call.

Edge cases and what we do

CaseWhat happens
Prospect already has an account (same email, phone or shop name)On add, the desk checks prospects, accounts, sign-ups, profiles and the website waitlist. Same email or phone as another prospect: refused, with a link to the existing one. Same email as an account: offered "link this account" instead. Same-looking name only: shown as a warning; Sales may still add.
Same customer from two places (waitlist and a walk-in)One prospect per waitlist row and one per account (unique keys). Importing the waitlist twice adds nothing new.
Customer never confirms their emailShown as stuck at step 2 with days waiting and when the last link went out. Sales can resend (at most 5 links an hour, same limit as the customer's own button) or confirm by hand after speaking to them. Both audited.
Customer with no adStep 5 says so and suggests a ready-made ad; Sales sets a next step "collect the ad". Nothing is uploaded in their name without them.
Customer cannot use a computerSales does the typing (hold, booking on behalf), records the customer's yes as an Agreed entry first. The customer pays themselves.
Who may see a customerEvery sales person sees the whole list (so two people never chase the same shop), and filters to "mine" by default. Only the owner, a Sales Manager or Admin may change a customer, write notes or log calls. An unowned prospect can be claimed by any sales person. Operations, Creative and Finance do not see the desk.
Handing a customer to another sales personOwner, Sales Manager or Admin picks the new owner. Logged as a Handover entry with a reason, and audited. The next step and its date move with the customer.
Sales person leavesAdmin deactivates their login. Their customers show "owner has left" on the team page; the Sales Manager moves them all to someone else in one go.
Two sales people claim the same prospectClaiming only works while the prospect has no owner (one database update with that condition). The second person is told who has it.
Prospect from the mall's own inviteSource "mall invite". Arrives unowned, so a sales person claims it. (The mall's invite page is another slice; it adds rows with this source.)
Price promise or discount beyond a sales person's limitThe desk does not set prices. It links to price requests and standing rates, where the existing rules and approvals apply. Notes must not promise a price; the quote is the promise.
Proposal goes stale because slots were soldA hold keeps slots out of sale until it ends; a quote without a hold does not. The desk lists quotes with no hold as "slots not kept" and holds ending within a day, so Sales acts before they go.
Ad sent back or refusedStep 6 shows the reviewer's reason and links to the ad on the review board. My day lists it.
Payment late or failedUnpaid bookings older than two days show on My day with a link to Unpaid payments. Sales chases; nothing about money is changed on the desk.
Campaign under-deliversThe desk shows plays so far and, only where a camera counted, people who looked ("not measured" otherwise). A booking that went live a day ago with no plays shows "Nothing has played yet". Free plays are granted through the existing bonus booking; the top-up rule itself belongs to the results slice.
Customer wants to stopClose as "stopped" with a reason. Cancelling a booking still goes through the bookings page and its refund rules.
Follow-ups forgottenEvery contact log entry may set the next step and date; it becomes the customer's next step. Overdue ones sit at the top of My day in red.
Customer has gone quietNo contact for 14 days and not playing: listed as "gone quiet".
What Sales must never see or doNo shopper phone numbers or wallet data on the desk (it never reads wallet tables). No change to ledgers, money rows or system settings. No logging in as the customer. Contact details are the business's own work contact.
Notes that contain personal detailsThe note box says "business facts only". Phone numbers and email addresses typed into a note or call log are removed before saving, and the person is told; the work phone belongs in the contact box.
Contact details in logs and the audit trailNever logged. The audit trail records that a contact detail changed, never the value.
Duplicate typing errors in phone numbersPhone numbers are compared on their last ten digits.

Screens

  • My day /ops/sales — what needs me today.
  • Customers /ops/sales/customers — prospects and signed-up customers, one list. Add, import the waitlist, filter by stage and owner.
  • One customer /ops/sales/customers/[id] — the path with one help action per step, contact log, owner and handover, campaigns with their numbers.
  • Team /ops/sales/team — Sales Manager and Admin: each person's customers by stage, stuck ones, owners who have left, bulk handover.
The Sales desk · Docs