HOCO B2B
Team tasksAkram

DQA-10 — Notification & message copy — push, SMS, email, WhatsApp texts

Short, consistent French copy for every event in the notification matrix and every share text, with Arabic placeholders.

FieldDetails
Task codeDQA-10
PhaseP1 — V1 build & integration
Product scopeV1
StatusPlanned
StartSun 22 Nov 2026
DueMon 23 Nov 2026
ResponsibleAkram — UI/UX designer
Co-responsibleAnis
Effort0.75 person-day(s) planned · 1.5 from scratch · size S
Area · appContent · design
Depends onDES-22
Unblocks—
Milestones—

Summary

Short, consistent French copy for every event in the notification matrix and every share text, with Arabic placeholders.

Description

Akram writes, with Anis, short and consistent French copy for every event in the notifications matrix (/docs/srs/notifications-matrix, about 70 template keys such as order.validated, order.refused, assisted_order.awaiting_confirmation, account.approved, return.received, ticket.resolved.replacement, tour.assigned, otp.code.signup). Each key covers its channels (in-app inbox, push, SMS, email), and the task also covers every share text and the live-status toasts, with Arabic keys as placeholders. Inputs: the notifications matrix (event, recipient, channel, category, deep link, template key), NOT-04 and IVT-02, the copy rules of the design system (vous, sentence case, no-break spaces) and the business-number formats. Limits: push title 40 characters or fewer and body 120 or fewer; SMS one GSM-7 segment; in-app title and body. Consumers: Anis's NotificationTemplate seed and BO-58, SRV-22 (invitation share texts) and the WhatsApp greeting of support.whatsapp, and Imad's ARB strings for toasts and share sheets (MOB-07).

Subtasks

#SubtaskOwner
1Export the template-key list from the notifications matrix into a copy sheet: key, event, recipient, channels, deep link, variables ({orderNumber}, {resellerName}, {amount}, {reason})Anis
2Order lifecycle copy (reseller, delegate, staff variants): submitted, validated, refused with reason, modified, preparing, ready / ready for pickup, shipped, delivered, cancelled, returned, delivery failed, confirmation overdueAkram
3Assisted orders, account and security: awaiting confirmation (SMS + push, 72 h deadline written out), reminder, confirmed, rejected, expired; pending validation, approved, rejected, suspended, customer type changed; OTP codes (signup, password reset, phone change), password changed, new deviceAkram
4Finance, returns and support: invoice issued or overdue, payment declared / confirmed / rejected; return requested / approved / rejected / received; ticket created / replied / waiting for your reply / resolved (replacement, return, credit note, repair) / rejected / closedAkram
5Field and staff: tour assigned / updated / cancelled / started / closed / reopened, visit not done, task assigned or due, invitation steps, promotion started, stock low or out, export ready or failed, import finished, daily digestAkram
6Share and support texts: invitation (WhatsApp, SMS) with https://app.hoco.dz/i/AB12CD34 and code AB12-CD34, product share, WhatsApp support greeting « Bonjour, je suis Bazar du Centre (REV-000123)… » and the guest greetingAkram
7Live-status toasts and banners: « Commande CMD-2026-000158 : Validée », « Votre commande a été modifiée par HOCO », reconnection and pause messagesAkram
8Length and charset checks: push title ≤ 40 and body ≤ 120 characters; SMS within 160 GSM-7 characters (no « », no ê / â / î / ô / û / ç); every variable rendered with its longest realistic valueAkram
9Add Arabic placeholder columns (empty, flagged) and English keys for later, with the same variablesAkram
10Import the copy into the template seed and BO-58 previews; check the deep linksAnis
11Map toasts and share-sheet strings to ARB keys in hoco_l10nImad
12Smart-notification copy (client document 03): titles, bodies and action labels of the V1 SN templates and their .grouped variants, the default action label of every existing reseller event, the decision on leading emojis; Arabic from the client's wording (/docs/srs/smart-notifications#copy)Akram

Deliverables

  • Copy sheet (CSV/JSON keyed by template key × channel) with French copy, variables and character counts
  • Share texts and the WhatsApp greetings, ready for SRV-22 and the reseller apps
  • Arabic and English placeholder columns with the same keys

Acceptance criteria

  • Every template key in the notifications matrix has copy for each of its channels
  • Push titles are 40 characters or fewer and bodies 120 or fewer; every SMS fits one GSM-7 segment
  • Every message names the object (order number, ticket, return) and the next action, and none implies automatic order confirmation
  • No message reveals a stock quantity or another reseller's price
  • Copy follows the house style (vous, sentence case, no exclamation marks except success titles)
  • Anis has imported the sheet into the template seed without missing keys

Requirements covered

RequirementTitleRelease
NOT-04Event → channel → recipient matrix and localised templatesV1
IVT-02Share by WhatsApp, SMS or link; copyable referral codeV1
NOT-10An action button (label and deep link) on every reseller notificationV1

Test measures

  • A script counts characters and GSM-7 compliance per row and reports violations
  • Render 10 key notifications on a real Android device (push and inbox) and read them aloud
  • Cross-check the key list against the notifications matrix: zero missing, zero orphan

Risks

  • The matrix changes during the build — key the sheet by template key and re-export the diff from the matrix before each import.

KPI

  • Delivered by Mon 23 Nov 2026 within 0.75 person-day(s).
  • Every acceptance criterion above demonstrated before hand-off; linked requirements' acceptance criteria pass.
  • Zero open critical defects, permission gaps or data-integrity regressions at sign-off.

Generated from content/plan/tasks.json by scripts/generate-team-tasks.mjs. Dates are computed by the scheduler (Sunday–Thursday weeks, holidays excluded) — change the plan, not this page.

On this page