Summit Coffee

Persona identity verification

The business owner completes Persona identity verification in their sub-account. This is a CLIENT action against an external provider — no real API integration is connected in this build, so it is an explicit operator-confirmed step. Sending the owner to Persona is NOT verification.

Evidence to mark complete: Persona session shows a passed/verified result in the sub-account. Do not mark complete until the verified outcome is visible — a started session is not identity verification.

10DLC brand registration

Forge registers the A2P 10DLC brand using the legal business name, EIN, and address collected during onboarding. Submission happens in the sub-account's messaging/A2P surface. The carrier (EXTERNAL) then reviews and approves — submission is not approval.

Evidence to mark complete: A2P brand status reads Approved in the sub-account. A Submitted status is not approval — do not mark this complete until the brand is Approved.

10DLC campaign + use case

Forge registers the A2P campaign with the transactional messaging use case. Messaging purpose: transactional messages related to account setup, onboarding, verification, billing and service status. Consent language: "I agree to receive transactional text messages from Forge regarding my account, setup, onboarding, verification, billing and service status.". The carrier (EXTERNAL) approves the campaign — submission is not approval.

Evidence to mark complete: A2P campaign status reads Approved. Submitted is not approved — do not mark complete until the campaign is Approved.

SMS-capable number

Forge provisions an SMS-capable number in the sub-account. This is the CLIENT's Perks messaging number — it is NOT the Forge owner-notification SMS lane (those are separate architectural boundaries). Provisioning a number is not the same as successful message delivery.

Evidence to mark complete: An SMS-capable number is assigned to the sub-account (record it below).

Customer-facing domain

Connect the customer-facing domain. Forge subdomain: Forge configures it. Client-owned domain: the client applies the DNS change. Forge-purchased domain: Forge registers it from the client's preferences and configures DNS (a manual Forge task — not automated). Mark connected only when the domain resolves to the Perks app.

Evidence to mark complete: Domain status is connected and the hostname resolves to the Perks app.

Send + verify a test message

With A2P approved and an SMS number available, Forge sends a test message and confirms receipt. A provisioned number alone is NOT delivery. If the sub-account's message/conversation history can confirm delivery, use that as evidence.

Evidence to mark complete: A test message was sent AND confirmed received (check the sub-account message history). A provisioned number alone is not delivery — do not mark complete without confirmed receipt.