Orders section gets tabs: Orders / Relocations / Requests (concierge sees the
last two). Relocation list with statuses, plan progress and current step;
relocation card with per-client steps (status, client comment, rename, add,
remove), documents, quiz answers, team note, write/call. Requests: website
cleaning requests and app requests (membership, call back) with notes,
create order, turn on membership. Dashboard links point here instead of the
old admin.
Fix: leads with an unanswered 'already moved?' (NULL) were skipped by
'moved not true' filters — plan sync and linking to the app client.
Client bot: after an order is done, asks for 1-5 stars; low rating asks what
went wrong, the reply is saved as the rating comment and goes to the team chat.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Profile with club card, plum theme for buttons/selections and the sticky total,
move screens with the full-width hero, services/docs headers, empty docs fix.
Promo code field: applies to the quote, shows why a code is rejected,
says when the membership discount is bigger.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Plum hero with a club-card ticket, a 'Now' block with the live order timeline,
new order cards and order screen, QR club card screen, new nav
(Home / Orders / Chat / Card / Profile). Clients rate completed orders
(1-5 stars + comment); provider rating is recalculated.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- Products: services with full setup — content (name, description, extras names
in 5 languages via text overrides), price tiers and extras, booking window,
late-cancel fee, on/off, checklist; category discounts by membership level;
membership plan prices; promo codes; relocation steps and documents.
- Text overrides: TextOverride table on top of the i18n files; API, bots and the
worker reload them every minute, mini apps fetch public.texts at start.
- Promo codes applied to orders (admin new-order form and client API): not
stacked with membership discount — the larger wins; once per client; validity,
limit and categories.
- Broadcasts to the client bot by any client filter, per-language texts with
Russian fallback, test to yourself, ~25 msg/s, per-recipient status, resume after
worker restart, history with progress and stop.
- Activity log (who/when/what, filters, details) and Settings page with all
owner settings grouped, plus payment methods.
- Tests for promo codes and text overrides.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- CRM: configurable pipeline (default: New → Contact → Meeting → Negotiation →
Connected / Lost), drag-and-drop board, lead card with call/meeting/note history,
photos and files, tasks with Telegram reminders at the due time, map of venues
(OpenStreetMap via Leaflet), lost reason. Sales reps see only their own leads.
- "Connected" in one click: a venue becomes a club card partner with a one-time
owner link to the work bot; an agency gets a code and a client link. The sales rep
is recorded on the partner for the bonus.
- Sales bonus formula in settings (per venue, per agency, % of revenue from the
rep's agency clients for N months); defaults are 0 until the owner sets them.
- Agencies (superadmin): clients, gift subscriptions, reward by month, payouts,
client link, edit. Venues: offers by membership level (5 languages), staff,
card checks, 8-week activity, owner link, map point.
- Schema: SalesStage/SalesLead/SalesActivity/SalesTask; salesId on Agency and
Partner; lat/lng/phone/note on Partner; agencyId on Payout.
- Tests for stage rules, conversion, task reminders and bonus; dev:crm-demo.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- Auto-assignment: a new order is offered to the best free provider (same ranking as
the dispatcher hint); a decline or timeout passes it to the next one; nobody is
offered the same order twice; after N tries it waits for a dispatcher and the team
is notified once. The worker retries waiting orders every minute. Settings
assign.auto / assign.maxAutoOffers (toggle on the Orders page, checkbox in old admin).
- Orders: list by day with groups (need a provider, offered, assigned, in progress,
done, cancelled), periods and search; order card with progress, provider or ranked
candidates ("offer" / "pick automatically"), details, checklist and photos,
history in plain words, client, money (superadmin), payment, status change,
reschedule (slots or custom time), cancel with fee.
- New order for a client (from the client card or the Orders page): params form,
address, free slots for 14 days, price with the client's discount.
- Providers: list with rating, orders, declines, low ratings, next order; card with
quality, ratings, upcoming orders, schedule and districts, admission documents,
block/unblock with reason, new bot link, money and payouts (superadmin).
- Payout gets paidAt/note/createdById; Provider gets blockedReason/blockedAt/adminNote
and documents (ProviderDoc).
- Tests for auto-assignment.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- Provider messages store the order that was current when they wrote: a started
order first, otherwise the nearest assigned one within -4h..+12h; none — "no order".
- Admin chat: order tag above each provider message, "now / next" order strip in
the conversation header, order number (or "no order") in the thread list.
- Telegram notification to the team gets an order line or "no current order".
- Test for the order-picking rule; demo shows both cases.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- ChatThread per client/provider and channel; messages get files, internal notes,
source (bot/mini app) and delivery errors; reply templates. Migration moves old
concierge messages into threads.
- Routing: subscribers write to the concierge, others to support; /support and
/concierge in the client bot; staff can take, transfer, close and move threads.
- Telegram: photos/documents from clients and providers, replies with the channel
header, files sent from storage, notifications only to the assignee or the
channel's staff, "Reply" into a specific thread.
- New admin: /chats with list, conversation, notes, files, templates, client panel;
"Message" button on the client card; dashboard counts threads awaiting reply.
- Client mini app: in-app chat screen sharing the same conversation.
- Old admin keeps working on the same data (notes hidden there).
- Tests for routing, notes, assign/close/move, lists, recipients; separate test DB
via TEST_DB_NAME; dev:chats-demo script.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
