Naser Mansour
0f9d12c3cf
Adds docs/tasks/ (16 epics + 102 stories converted to task/subtask files with statuses.md as the new status source of truth) and docs/ux-design.md (retrospective design-system reference), and points CLAUDE.md at them. docs/prd.md and docs/architecture.md are kept as BMAD wrote them; the legacy docs/stories/, docs/epics/, docs/qa/gates/ and .bmad-core/ stay in place as historical/traceability records, superseded but not deleted. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
1.5 KiB
1.5 KiB
id, title, status, date, parent
| id | title | status | date | parent |
|---|---|---|---|---|
| 8-3 | 8-3 Booking Submitted Confirmation | QA Review | 2026-09-27 | 8 |
Description
As a client, I want to receive confirmation when I submit a booking request, So that I know my request was received and what to expect next. Send the email after successful consultation creation. Typical location:. Full implementation history: docs/stories/story-8.3-booking-submitted-confirmation.md
Acceptance Criteria
- Sent immediately after successful consultation creation
- Consultation status: pending
- Email queued for async delivery
- Subject line: "Your consultation request has been submitted" / "تم استلام طلب الاستشارة"
- Personalized greeting with client name
- "Your consultation request has been submitted" message
- Requested date and time (formatted per user's language preference)
- Problem summary preview (first 200 characters, with "..." if truncated)
- "Pending Review" status note with visual indicator
- Expected response timeframe: "We will review your request and respond within 1-2 business days"
- Contact information for questions
- Email sent in client's
preferred_language(default: 'ar') - Arabic template for Arabic users
- English template for English users
- Uses base email template from Story 8.1
- No action required message (informational only)
- Professional template with Libra branding
- Gold call-to-action style for "View My Bookings" link (optional)