Skip to content

Pilot Support Operating Procedure

Last audited: 2026-06-25.

This procedure defines how MamNajem handles support during the first paid pilot. It is sized for a small controlled cohort, not a broad public launch.

Operating Owner

The Product Owner owns pilot support. The first person who sees a support item owns it until they either resolve it or explicitly hand it to another owner.

For SEV1 and SEV2, switch to the Incident Response runbook. Assign:

  • Incident owner: coordinates timeline, decisions, and user updates.
  • Technical lead: investigates and fixes.
  • Communications owner: sends user-facing updates.
  • Scribe: records timestamps, evidence, and follow-ups.

Support Channels

Primary authenticated channel:

  • Mobile app: Account -> Support -> Report problem
  • Mobile app shortcut: Report problem
  • Admin review surface: web-admin Problem Reports

Primary email channel:

  • [email protected]
  • Use when the user cannot sign in, cannot reach the app, replies to a pilot check-in, or needs billing/account help before an in-app report exists.

Pilot check-in channel:

  • Weekly pilot check-in call or email thread.
  • Any actionable issue raised in a check-in must be copied into the support log on the same day.

Do not run support only from private chat. If a user writes through private chat, acknowledge there, then copy the issue into the support log and continue from email or in-app report.

Response Targets

Business hours: Monday-Friday, 09:00-17:00 Europe/Warsaw.

Class Examples Acknowledge by Update cadence
P0 incident production unavailable, login broken for cohort, payment/subscription corruption, data exposure 10 minutes every 30 minutes until stable
P1 blocker tenant cannot join active pilot lease, payment proof lost, handover cannot be confirmed, account deletion/export fails 4 business hours daily until resolved
P2 support how-to question, billing portal confusion, invite resend, status explanation 1 business day every 2 business days if still open
P3 feedback feature request, copy confusion, non-blocking UX issue 3 business days batch into weekly review

If the target will be missed, send a short update before the target expires and set a concrete next update time.

Triage Flow

  1. Open support inbox and web-admin Problem Reports twice per business day.
  2. Assign class P0, P1, P2, or P3.
  3. Confirm environment: integration, production, or local/user device.
  4. Identify user role: owner, tenant, public lead, admin.
  5. Use Pilot support macros for first reply when the issue matches a known case.
  6. Check web-admin for allowlist, problem reports, Stripe webhooks, processed webhooks, and relevant admin views before asking the user for more data.
  7. If technical evidence points to an app/backend/infrastructure issue, escalate with the log fields below.
  8. Close only after the user-visible state is fixed, a workaround is accepted, or Product Owner marks the issue out of scope.

Web-admin problem report status mapping:

  • OPEN and IN_PROGRESS are open support work.
  • RESOLVED and DISMISSED are closed support work.
  • Use RESOLVED when the user-visible issue is fixed or explained.
  • Use DISMISSED only when the item is duplicate, unsupported, spam, or not actionable after review.

Escalation Path

Use this order:

  1. Product Owner: classify issue, send macro, decide customer posture.
  2. Admin tooling: check allowlist, problem report, account/payment/lease state, and webhook recovery surfaces.
  3. Backend Developer: API errors, data integrity, webhook, subscription, payment, export, deletion, email, or notification failures.
  4. Frontend Developer: mobile/web-admin UI mismatch, broken navigation, upload UI, login screen, or visible copy issue.
  5. Infra Developer: deploy, DNS, TLS, CloudWatch alarm, database, storage, email provider, or environment configuration issue.
  6. Incident response: any P0, repeated P1, security/privacy concern, or payment/subscription corruption.
  7. Counsel/Product Owner review: any user asks for legal effect, statutory notice, lease enforceability, deposit dispute advice, eviction, rent increase, or formal claim wording.

What To Log

Every support item must have one log row or ticket containing:

  • Support case ID or problem report ID.
  • Channel: in-app report, support email, pilot check-in, private chat copied into log.
  • Created time and latest update time in Europe/Warsaw.
  • Environment and app version/build when known.
  • User role and contact email.
  • Product area: invite, payment proof, handover, billing, export, deletion, Stripe rent payment, login, support report, other.
  • Severity/class: P0, P1, P2, or P3.
  • Macro used, if any.
  • User-visible symptom in one or two sentences.
  • IDs needed for support: problem report ID, property ID, lease ID, payment request ID, handover protocol ID, subscription/customer ID, Stripe checkout session/payment intent/event ID, request ID, correlation ID, spawn ID.
  • Current status: open, waiting_on_user, waiting_on_engineering, monitoring, closed_resolved, closed_dismissed, or closed_out_of_scope.
  • Owner and next update time.
  • Final resolution and follow-up owner, if any.

Never log:

  • Passwords, MFA codes, recovery codes, raw auth tokens, full card numbers, bank login data, full Stripe payloads, private message bodies not needed for diagnosis, or unnecessary copies of uploaded legal/financial documents.

Close Criteria

Close as closed_resolved when:

  • User-visible state is fixed or explained, and
  • user has the next action or confirmation, and
  • any backend/admin state was verified when the issue involved data, payment, subscription, export, deletion, webhook, or invite linkage.

Close as closed_dismissed when:

  • The report is duplicate, non-actionable, spam, or expected behavior, and
  • the user has a short explanation if they need one.

Close as closed_out_of_scope when:

  • The request asks for legal advice, unsupported lease/legal automation, property management work outside the product, or custom enterprise workflow beyond first pilot scope.

Stop Conditions

Pause new pilot onboarding and review scope when any condition is true:

  • Any SEV1 production incident.
  • Any suspected data exposure, destructive data loss, or privacy incident.
  • Two payment, billing, subscription, or account-deletion integrity incidents in 7 days.
  • Three users hit the same P1 blocker in 7 days.
  • More than 10 open support items remain unresolved at end of a business day.
  • Product Owner misses response targets for two P1 issues in the same week.
  • Support work exceeds 4 founder hours in one week for a cohort of 3-5 landlords.
  • A legal-boundary question repeats enough that current product copy may be misleading.

When a stop condition triggers:

  1. Stop inviting new pilot users.
  2. Finish support for active users.
  3. Open an incident or pilot risk record.
  4. Decide: fix now, narrow pilot scope, add support staffing, or pause pilot.
  5. Record the decision in the pilot weekly review.

Daily Checklist

Morning:

  • Check [email protected].
  • Check web-admin Problem Reports.
  • Check open P0/P1 items and next update times.
  • Check New Relic/CloudWatch only when support symptoms suggest product failure.

Afternoon:

  • Send due updates.
  • Close resolved items.
  • Escalate stale P1 blockers before end of business day.
  • Add repeated questions to the weekly review.

Weekly Review

At the weekly pilot check-in, record:

  • Count of support items by class and product area.
  • Median first response time.
  • Open P1 blockers.
  • Repeated macro usage that signals product/copy confusion.
  • Any stop condition or near miss.
  • Whether to continue, narrow, pause, or expand the pilot cohort.

Evidence

EP7-T5 is complete when this procedure is linked from pre-release docs and the Product Owner can use it to run one week of pilot support without inventing a new process.