bolor.
Photoxpedia IDPrivate services, provider control

Case study · Problem, research, and product direction

Less coordination. More time to deliver the service.

For solo providers and micro or small businesses, delivering the service and managing demand compete for the same limited time. Photoxpedia aims to make it easier for customers to reach the right provider while giving providers control over requests, timing, and access.

Service-detail visibilityThree optionsDesktop layout proposal
Choose what a visitor sees

How private is this service?

Public detailsAnyone can read the description, rate, and terms.
Approval requiredShow the short listing. Share details after you approve a request.
Contact exchangeAsk the visitor to exchange contact details through your card.
The exchange link carries a service ID, but the connect flow does not currently use it to grant service access.
Use approval required

A provider’s story

Jordan gives a new client a card after a referral.

Jordan is a portrait photographer. Her card should explain what she does and let a client ask about headshots. It should not reveal her private contact details or full service terms before she knows what the client needs.

What it is

A private service doorway attached to a Photoxpedia profile or card.

Why it exists

Some providers need to understand a visitor’s intention before sharing direct details or sensitive service information.

What it solves

The visitor can request access; the provider reviews it; approved people get the next step. This page checks whether the current product really completes that promise.

Design tools and technology

DesignFigma · Note · Sketches
AI-assisted developmentCodex · Claude · Perplexity
ApplicationNext.js · React · TypeScript
InterfaceTailwind CSS
DatabasePostgreSQL · Drizzle ORM
Hosting and storageVercel · Vercel Blob
AuthenticationAuth.js
EmailNodemailer
My role
Sole designer, developer, and researcher
Ownership
End-to-end product development
Research
Interviews with solo and small business owners and service providers
Product status
Shipped · broader validation in progress

01 · The problem

The work cannot stop every time the phone rings.

A provider in a session cannot always answer a call, explain an offering, or coordinate the next appointment. Customers need an easy way to understand availability and ask for a service; providers need to handle those requests around the work they are already doing.

Booking tools, online availability, and communication often become separate pieces to assemble. Third-party fees, learning curves, and dependencies add cost and setup work to an already full schedule.

02 · What I heard

Finding and connecting the tools is another job.

I interviewed solo and small business owners and service providers. They described having little time to browse, compare, and find a solution that fits their business. Available options felt expensive or difficult to use, and bringing the pieces together required too many dependencies.

These interviews informed the problem framing and product direction. The four people below are scenario personas used to explore the journey, rather than individual interview participants.

03 · The product direction

Make the next step easy for both sides.

The goal is a simple way to fill available time slots and connect customer demand with a provider’s capacity. A customer should be able to find the service, explain what they need, and reach a clear next step. A provider should be able to review and respond without interrupting a session.

Convenience has to preserve control. Services have different expectations: some can be openly described, while others require privacy, exclusivity, or a review of the customer’s intention before details are shared. This journey explores that approval-required branch.

04 · Ownership and learning

One owner from research through implementation.

I owned the research, product design, development, and end-to-end delivery. That scope connected the interview findings to the experience and its implementation, including the relationship between profile privacy, service visibility, and ongoing access.

The product has shipped. I am waiting for more people to use it and validate the experience; validation findings and measured outcomes have not been announced. Easier coordination, customer convenience, and provider control remain intended benefits, not demonstrated results.

Four people in this journey

The same card has to make sense to each person without forcing the provider to publish sensitive details.

Scenario personas for this design journey; motivations and habits below are design definitions, not user-research findings.

Service provider · account owner

Jordan, portrait photographer

Gets referrals from real estate agents and offers personal-branding headshots. Wants to understand the request before exposing her phone, home studio details, or full terms.

Needs: private profile, service request inbox, and clear approve/decline controls.

Motivation
Protect boundaries while growing a referral business.
Context and habits
Checks requests between sessions on mobile; manages offerings and longer replies at a desk.
Friction
Unknown intent, accidental disclosure, and ambiguous publishing controls.
Success looks like
Can review who is asking and grant only the service access she intends.

Off-network visitor · guest

Alex, real estate agent

Scans Jordan’s printed QR after a referral. Has no Photoxpedia account and wants a headshot for a new property listing profile.

Needs: see who Jordan is, explain the request, and know what approval actually gives access to.

Motivation
Find a trusted photographer and understand the next step quickly.
Context and habits
Starts from a printed QR on a phone; may follow the approval email from a desktop inbox.
Friction
Forced signup before asking a question; approval that leads back to a locked page.
Success looks like
Knows what was approved and can reach a usable next step without resubmitting.

Existing network member

Sam, signed-in client

Already has a Photoxpedia account and scans the same card. Wants to request details without repeating their identity information.

Needs: a clear request, status, and access that stays available after approval.

Motivation
Use an existing identity to request and retain access.
Context and habits
Signed in on mobile or desktop; returns to the same service after a decision.
Friction
Repeated identity fields and an unrelated Services switch blocking an approved request.
Success looks like
Can see request status, reopen approved details, and propose a call.

First-time prospective member

Riley, invited provider

Requests an invitation, is reviewed by an admin, then joins to publish a service of their own. They may later become a client of another member too.

Needs: a guided account setup and a clear split between profile privacy and service privacy.

Motivation
Join the network and confidently publish a first offering.
Context and habits
Starts with an invitation request; uses desktop for setup and mobile for ongoing review.
Friction
Confusing invitation versus sign-in, and profile privacy versus service privacy.
Success looks like
Claims the invitation, understands both privacy controls, and shares a usable service card.

One card, four journeys

Read each lane from left to right: the trigger, the action, the decision, and the next step. The provider’s decision joins the guest and member paths.

Journey stages → Blue: current path · Red: current obstacle · Dashed amber: proposed completion
Person01 · Enter02 · Act03 · Review / wait04 · Outcome05 · Next step
JordanProvider · owns the decision
PrepareSets profile/contact privacy; enables Services.§2 · Profile setup
Publish and shareCreates an approval-required offering and shares her card.§3 · Save draft currently creates live
ReviewReads guest or member intent in the service inbox.§3–4 · Provider inbox
DecideApproves access or declines; details stay gated on decline.§5 · Approval outcome
ContinueReviews the proposed call time; accepts or declines.§5 · Expected call
AlexGuest · no network account
DiscoverScans Jordan’s QR after a referral.§3 · Live card
AskEnters name, email, and a short intention.§4 · Guest request
WaitSees confirmation; decision email needs SMTP.§4 · Request received
Approval blocksEmail links back to the gate; no guest membership exists.§5 · Guest blocked state
Claim accessProposed: verify approved email, join/sign in, link membership.§5 · Recommended, not built
SamMember · known identity
DiscoverOpens the same card while signed in.§3 · Live card
AskSends intent with existing account identity.§4 · Own Services switch required
WaitPending status remains associated with the account.§4 · Request received
ReadApproval creates membership; own Services switch still gates details.§5 · Member approved
ContinueSuggests a call time, or checks in to a class session.§5–6 · Call / class branch
RileyProspective provider · new account
ApplyRequests an invitation; admin reviews the request.§1 · Request invitation
JoinReceives invite and claims it with a password.§1 · Email requires SMTP
ConfigureSets profile privacy separately from service visibility.§2 · Privacy controls
OfferCreates a service; current save publishes immediately.§3 · Publishing mismatch
ParticipateReviews requests as a provider; follows Sam’s path as a client.§4–6 · Both roles

Decline is a complete alternative outcome: access remains hidden. Approval to a service does not automatically expose Jordan’s private profile contact fields. The proposed guest claim step is still a product gap.

The workflow behind Jordan’s story

Blue is present in code. Amber depends on configuration or reveals a behavior mismatch. Red marks a broken or incomplete privacy path.

Implemented in source Works when email or database is configured Missing or behavior mismatch Different visitor path

Provider joins and publishes a service

Signup begins with an invitation claim. Magic link is a later sign-in option for an existing account.

flowchart TD
  start["Provider finds Photoxpedia ID"]:::current --> ask["Request invitation with email"]:::current
  ask --> review["Admin reviews request"]:::current --> approved{"Invitation approved?"}:::decision
  approved -->|No| wait["Wait for review; no account yet"]:::current
  approved -->|Yes| invite["Admin sends invite link"]:::config
  invite --> claim["Claim invite: name, email, password"]:::current
  claim --> dashboard["Account created; dashboard opens"]:::current
  dashboard --> profile["Create profile and contact privacy"]:::current
  profile --> addon["Turn on Services in profile settings"]:::current
  addon --> offer["Create a service or class"]:::current
  offer --> privacy{"Choose service visibility"}:::decision
  privacy -->|Public| public["Details are public"]:::current
  privacy -->|Approval required| permission["Visitor requests access"]:::current
  privacy -->|Contact exchange| exchange["Connect form; no service access grant"]:::gap
  offer -.->|Button says Save draft| live["Current action saves as live immediately"]:::gap
  signin["Later: password or magic link sign-in"]:::config -.->|Existing accounts only| dashboard
  classDef current fill:#f1f6ff,stroke:#1264e8,color:#172033,stroke-width:1.5px;
  classDef config fill:#fff9e8,stroke:#c2962c,color:#4f3d15,stroke-width:1.5px;
  classDef gap fill:#fff2f3,stroke:#c7616d,color:#702e38,stroke-width:1.5px;
  classDef decision fill:#ffffff,stroke:#8794a8,color:#172033,stroke-width:1.5px;
        

Visitor requests details, then decides what to do

Account holders and guests can ask for access, but only the account path creates a service membership today.

flowchart TD
  card["Visitor scans card or opens profile"]:::current --> service["Opens service listing"]:::current
  service --> visibility{"Service visibility?"}:::decision
  visibility -->|Public| details["Read details, rate, and terms"]:::current
  visibility -->|Contact exchange| connect["Submit contact form"]:::current --> exchangeGap["Service ID ignored; no access grant"]:::gap
  visibility -->|Approval required| prompt["See title and generic request prompt"]:::current
  prompt --> identity{"Signed in?"}:::decision
  identity -->|No| guestForm["Enter name, email, and short intention"]:::current
  identity -->|Yes| addon{"Requester has Services enabled?"}:::decision
  addon -->|No| blocked["Request is blocked by own add-on switch"]:::gap
  addon -->|Yes| memberForm["Send short access request"]:::current
  guestForm --> inbox["Request saved; provider sees it in Services inbox"]:::current
  memberForm --> inbox
  inbox -.->|Email alert needs SMTP| ownerMail["Provider receives request email"]:::config
  inbox --> decision{"Provider approves?"}:::decision
  decision -->|Decline| no["Request declined; detail stays hidden"]:::current
  decision -->|Approve account| member["Create service membership + contact"]:::current
  member --> memberGate{"Requester’s Services switch still on?"}:::decision
  memberGate -->|Yes| private["Member can read service details"]:::current
  memberGate -->|No| memberBlocked["Approved, but own add-on still gates details"]:::gap
  private --> serviceKind{"What happens next?"}:::decision
  serviceKind -->|Service| callRequest["Member suggests a call date and time"]:::current
  callRequest --> callDecision{"Provider accepts the time?"}:::decision
  callDecision -->|Yes| expected["Expected call is confirmed"]:::current
  callDecision -->|No| callNo["Expected call is declined"]:::current
  decision -->|Approve guest| contact["Owner contact record only; no membership"]:::gap
  contact --> guestEmail["Email links to regular service page"]:::config
  guestEmail --> guestBlocked["Guest still cannot read gated details"]:::gap
  guestBlocked -.->|Recommended next step, not built| claimGuest["Guest claims or creates network account"]:::config
  claimGuest -.->|Provider grants approved membership| approvedMember["Create service membership + contact"]:::config
  serviceKind -->|Class| session["A dated class session is available"]:::current
  session --> checkin["Approved member self checks in"]:::current
  classDef current fill:#f1f6ff,stroke:#1264e8,color:#172033,stroke-width:1.5px;
  classDef config fill:#fff9e8,stroke:#c2962c,color:#4f3d15,stroke-width:1.5px;
  classDef gap fill:#fff2f3,stroke:#c7616d,color:#702e38,stroke-width:1.5px;
  classDef decision fill:#ffffff,stroke:#8794a8,color:#172033,stroke-width:1.5px;
        

Screens in the order people meet them

The device frames are static design examples, not connected UI. Use each section’s toggle to compare mobile and proposed desktop layouts. Scroll inside a phone for longer content; on a narrow display, desktop previews scroll horizontally. Blue labels mean the route or action exists; amber and red notes call out setup dependencies and behavior that needs a product decision.

1 · Join the network

Signup and returning sign-in are separate paths.

Try the other view ↗
Request an invitationImplemented
PPhotoxpedia IDA private network

A card that keeps your choices yours

Request an invitation

Tell us where to send yours. An account is created only after an invitation is approved and claimed.

Email addressyou@example.com
Optional noteWhat brings you here?
Request invitation
Request is reviewed by an admin. This does not create an account or sign you in.

Public request form → pending invite request. An admin must issue the actual invitation.

Invitation request receivedImplemented
Photoxpedia IDJourney state
✓

Your request is in

Riley’s invitation request has been submitted for review.

Emailriley@example.com
This is an invitation request, not an account. Wait for an invitation email before claiming your place.
Close

The request-invite modal has a completed state after a successful API response. No immediate signup or guaranteed review time is promised.

Invitation emailEmail configured
InboxToday

Photoxpedia ID · invitation

You’re invited.

Your invitation is ready. Use the button below to create your account.

Claim invitation
Invitation linkphotoxpedia.id/claim/••••••
Email delivery requires SMTP. An admin can resend an unused invite.

The invite carries a one-time code. Sending succeeds only when email is configured.

Claim invitationImplemented
PFinish signupInvite valid

Create your account

Use the invited email address to claim your place.

Your nameJordan Lee
Emailjordan@example.com · locked when invite is email-bound
PasswordAt least 8 characters
Confirm passwordEnter it again
Create account
This is password-based signup. A magic-link-only signup screen does not exist.

Claim creates the user, marks the invite used, and signs the new account in.

Invalid invitationImplemented
Photoxpedia IDJourney state

Invite not found

This invitation code does not match an invitation.

Back home

The claim page renders this error for a code that does not exist. It does not provide an invitation-expiry check.

Invitation already usedImplemented
Photoxpedia IDJourney state

Invite already used

This invitation has already been claimed.

Back home

The claim page renders a used-invitation error when usedAt is set. Use the existing sign-in route to return to an account.

Claim form validationImplemented
Photoxpedia IDJourney state

Create your account

Password••••••••
Confirm password•••••••
Passwords must match. A password shorter than 8 characters is also rejected.
Create account

The existing claim form shows inline errors for short or mismatched passwords and errors returned by the claim action. This is a form state, not a separate route.

Sign in laterExisting accounts
PWelcome backSign in

Use your email

Email addressjordan@example.com
Email me a sign-in link
Or use your password••••••••••
Sign in with password
Magic links are single-use and expire after 15 minutes. The email button appears only when SMTP is set up.

A separate returning-user path. It does not replace the invite claim form.

Source accuracy: when SMTP is unavailable, the magic-link fields and button remain visible but disabled, with an unavailable message.

Magic-link email requestedEmail configured
Photoxpedia IDJourney state
✓

Check your email

If an account exists for that email, a sign-in link will arrive shortly.

Emailjordan@example.com
The same login form shows this confirmation. It does not reveal whether this email has an account.

The login form sets magicSent after a successful sign-in request. SMTP is required; this is for existing accounts.

Sign-in error and email unavailableImplemented
Photoxpedia IDJourney state

Use your email

Emailjordan@example.com
Password••••••••
Invalid email or password.
Sign in with password
When SMTP is absent, the magic-link fields and email button remain visible but disabled. Password sign-in remains available.

The login form has invalid-credentials and magic-link request errors. Email-disabled state is shown separately from credential failure in the real form; both recovery conditions are illustrated here.

2 · Set up the provider profile

Profile privacy and service-detail privacy are separate controls.

Try the other view ↗
Profile and contact privacyImplemented
ProfileSaved privately

Your public identity

Make your profile useful

NameJordan Lee
What you doPortrait photographer
Short introductionHeadshots and personal branding portraits for local professionals.

Contact details

EmailConnect only
PhoneHidden
Profile visibility is a separate switch. Contact fields can be public, connect-only, or hidden.
HomeContactsProfile

Current profile editor stores contact values with a visibility rule.

Turn on ServicesImplemented
Profile settingsOptional feature

Your profile controls

Private services

Offer a service or class from a card. Decide how much detail visitors can see.

ServicesOn
Turning it on reveals the Services workspace. Turning it off hides the feature; saved offerings remain in the account.
Save setting
HomeContactsProfile

This per-profile switch is the actual access gate in current server code.

Service-detail visibilityThree options
Choose what a visitor sees

How private is this service?

Public detailsAnyone can read the description, rate, and terms.
Approval requiredShow the short listing. Share details after you approve a request.
Contact exchangeAsk the visitor to exchange contact details through your card.
The exchange link carries a service ID, but the connect flow does not currently use it to grant service access.
Use approval required

Use “Approval required” for the private-provider journey shown in the next screens.

3 · Create and publish the service

Check this before sharing the card.

Try the other view ↗
First offering workspaceImplemented
Photoxpedia IDWorkspace

Your services

No offerings yet.

New offeringType, title, description, visibility, rate and terms
Save draft
The current action publishes immediately even though the control says Save draft.

My memberships

No memberships yet.

The Services route implements empty owned-offering and membership lists alongside the creation form.

New service or classButton mismatch
ServicesNew offering

Describe the service

Offering typeService ▾
CardProfessional photography ▾
TitlePersonal branding portraits
Description shown to visitorPrivate portrait sessions for local professionals.
Rate · optionalFrom $350
Terms · optionalBy appointment
VisibilityApproval required ▾
Save draft
The server action currently creates this as live immediately. The button says “Save draft,” and there is no pre-publish confirmation.

The creator can choose a card, service/class type, description, rate, terms, and visibility. There is no separate public teaser field in this form.

Manage a live serviceImplemented
Photoxpedia IDWorkspace

Owner workspace · Live

Personal branding portraits

Pause
Archive
TitlePersonal branding portraits
DescriptionPrivate portrait sessions for local professionals.
RateFrom $350
TermsBy appointment
VisibilityApproval required
Save changes

Creation redirects to the service management page. The owner can edit the offering and change its status; there is no intervening draft review screen.

Paused serviceImplemented
Photoxpedia IDWorkspace

Owner workspace · Draft

Service paused

The offering is saved in Jordan’s workspace but is no longer a live public listing.

Publish
Archive
The application stores pause as draft. Existing memberships are not automatically removed.

setPrivateServiceStatus writes draft on Pause. Public service lookup only returns live offerings; the authenticated member route does not separately enforce live status.

Archived serviceImplemented
Photoxpedia IDWorkspace

Owner workspace · Archived

Archived offering

Jordan can still manage this offering from her workspace.

Publish
TitlePersonal branding portraits
Save changes
Archive does not delete the service or revoke its existing memberships.

The owner page shows the archived status and a Publish control for non-live services; archive is not permanent deletion.

Share profile link and QRImplemented
Photoxpedia IDWorkspace

Share your profile

Example scan targethttps://photoxpedia.id/jordan
Copy link
Download SVG
Source tagBusiness card
This QR encodes the example profile URL, not a private-access token or a service-specific URL.

The QR workspace provides a profile QR, SVG download, source tags, and copy feedback. This documentation uses a genuinely encoded example QR; Jordan’s handle is scenario content.

Provider’s service inboxImplemented
Services2 waiting

Requests to review

New people are asking

Alex Morgan
alex@example.com
Today
Why they reached outI need a headshot for my real estate profile. Can you share your process?
Approve and grant access
Decline request
The owner sees the requester’s name/email and their note in the dashboard.
HomeRequestsProfile

The inbox is on `/app/services`; the provider can approve or decline.

Live card and service pageImplemented
JJordan LeeProfile · public

Portrait photographer

Personal branding portraits

View service details

Approval required

The provider reviews each request before sharing the full service details.

What are you looking for?Your name, email, and a short reason for your request.
The profile button shows the service title. The gated page uses a generic request prompt, not a provider-written teaser.

The service page is linked from the selected card. “Pause” removes it from live listings.

4 · Visitor request and provider decision

Both visitor types reach the same owner inbox.

Try the other view ↗
Visitor who is not a memberGuest request
Jordan Lee · ServicePrivate details

Approval required

Personal branding portraits

The provider reviews each request before sharing the full service details.

Your nameAlex Morgan
Email addressalex@example.com
What are you looking for?I need a headshot for my real estate profile.
Send request
No account is required for this request. Keep the note brief; it is limited to 240 characters.

Anonymous request stores name, email, and intention, then notifies the provider if SMTP is configured.

Visitor with an accountMember request
Jordan Lee · ServiceSigned in

Approval required

Ask to see the full details

Your account name and email will be included with your request.

What are you looking for?I need a headshot for my real estate profile.
Send access request
Current code also requires the requester’s own Services add-on to be enabled. That requirement is easy to miss and should be reviewed.

Signed-in requests create a pending row associated with the requester’s user account.

Request receivedAlert depends on SMTP
Request sent
✓

The provider has your request

You’ll hear back after they review it.

For an account holder, the page can show pending status. For a guest, the confirmation appears after submission, but no account is created.
Back to Jordan’s profile

Request data saves before email is attempted. An SMTP failure does not undo the request.

Returning to a pending requestImplemented
Photoxpedia IDJourney state

Approval required

Personal branding portraits

Your request is waiting for the owner.

The private details are still hidden while Jordan reviews the request.

The public service route renders pending status for an authenticated requester; it replaces the request form. This is a return visit, not just submission confirmation.

Member blocked by own Services switchCopy mismatch
Photoxpedia IDJourney state

Request access

This private feature is limited to invited pilot accounts.
That is the current displayed copy. The actual condition is this visitor’s own Services switch being off. The gate has no direct enable-Services action.

Source checks canUse from the requester’s services_enabled flag; the page displays the pilotOnly translation. This screen documents the existing mismatch rather than inventing a recovery button.

Public service details · alternate pathPublic visibility
Photoxpedia IDJourney state

Public service

Personal branding portraits

Portrait sessions for local professionals.

RateFrom $350
TermsBy appointment
Sign in to request this service.
Sign in

For public visibility, guests can read description, rate, and terms. The sign-in link preserves the service URL as callback; signed-in visitors can request a call without service-access approval.

Contact exchange · alternate pathGeneral contact flow
Photoxpedia IDJourney state

Connect with Jordan

NameAlex Morgan
Emailalex@example.com
Phone · optionalYour phone
Company · optionalReal estate agency
NoteInterested in a headshot
Share contact details: selected. Consent to contact: optional. A suggested call can also be requested.
Send contact details

The exchange-visibility gate links to the Connect form. This is a general contact exchange; its service query parameter does not create service membership.

Contact exchange receivedGeneral contact flow
Photoxpedia IDJourney state
✓

Thanks for connecting

Your contact details have been submitted to Jordan.

Back to profile
This confirmation does not unlock approval-required service details.

The Connect flow navigates to /[handle]/connect/thanks. Do not interpret a saved connection or optional call request as service-access approval.

Service unavailableRecovery proposed
Photoxpedia IDJourney state

This service is unavailable

The offering may no longer be live or the profile may no longer be available.

Return to profile
Proposed recovery copy. The application currently renders not-found when the public lookup fails; this explanation and recovery action are not implemented.

Missing listing, non-public profile, or provider Services being off can make the public route return not-found. The precise reason should not be disclosed indiscriminately.

5 · Approval outcome

This is where member and guest requests currently diverge.

Try the other view ↗
Account holder approvedMembership created
Access approvedJordan Lee
✓

You’re approved

Jordan approved your request to view Personal branding portraits.

Private service detailsSession options, preparation notes, rate, and terms appear here.
Request this service
Current page access also checks that this visitor’s own Services switch is on. Approval alone may not be enough.

For signed-in members, approval adds a service membership and a contact record. The detail page offers an expected-call request.

Returning to My membershipsImplemented
Photoxpedia IDWorkspace

Sam · signed in

My memberships

Personal branding portraitsPrivate session description and preparation details.
These are active service memberships. The current membership card shows private details but has no Open service control.

The Services workspace lists active memberships and privateDetails. Reopening the public service URL is a separate path; do not draw a nonexistent detail link on this card.

Suggest a call timeExpected call
Request this serviceTo Jordan

When can you talk?

Suggest a time for a short call. Jordan will confirm or decline it.

Date and timeTomorrow · 12:00 PM
Note · optionalPersonal branding headshot
Send call request
This is not an availability-backed booking. The visitor proposes a date/time; the provider must approve it.

The current expected-call form uses a date/time picker and optional note. It does not offer selectable provider slots.

Call request sentImplemented
Photoxpedia IDJourney state
✓

Your call request was sent

Jordan will review the suggested time.

Close
This is the completed state of the inline call form, not a confirmed appointment.

CallRequestButton sets done after createCallRequest succeeds. The application does not render a persistent outgoing-call status page in this flow.

Provider confirms the callImplemented
Dashboard · Requests1 new

Expected call request

Alex Morgan

Suggested timeTomorrow · 12:00 PM
NotePersonal branding headshot
Accept this time
Decline request
Accepting confirms the expected call. Email alerts depend on SMTP configuration.

The provider handles expected calls in the dashboard request panel, separately from service-access approval.

Identity context: this existing Alex example applies once Alex has a signed-in account. Sam is the signed-in client used in the new private-service call outcome screens; guest service approval alone does not enable this path.

Provider’s upcoming expected callImplemented
Photoxpedia IDWorkspace

Jordan · Dashboard

Expected calls

Sam · confirmedTomorrow · 12:00 PM
NotePersonal branding headshot
Accepted requests remain in the provider’s upcoming-call list. This does not supply a video link or an availability calendar.

The dashboard call panel displays upcoming approved rows after the provider accepts. Sam is the signed-in requester in this private-service example.

Call accepted · requester emailEmail configured
Photoxpedia IDJourney state

Inbox · To Sam

Jordan accepted your call

Suggested timeTomorrow · 12:00 PM
NotePersonal branding headshot
This is the approval email outcome. Delivery needs SMTP; no persistent client status screen is implied.

sendCallRequestRespondedEmail sends approval details to the requester. This email confirms the proposed call time, separately from service-access membership.

Call declined · requester emailEmail configured
Photoxpedia IDJourney state

Inbox · To Sam

Jordan declined this call

Proposed timeTomorrow · 12:00 PM

This call time was not accepted.

Declining the call does not remove Sam’s approved service membership. The decision email depends on SMTP.

The call response action marks the request declined and attempts an email. It does not automatically reschedule or revoke service membership.

Guest approved · blocked stateAccess path missing
Approval emailTo Alex

Jordan Lee approved your request

Your request was approved

The current email links to the public service URL.

View service
A guest has no service membership or signed-in identity. Opening this URL still shows the request gate; there is no secure guest-access token or “claim this access” step.
Proposed: join the network to claim approval

The owner gets a contact record, but the guest does not become a service member and cannot see private details.

Guest claims approved accessRecommended · not built
PPhotoxpedia IDPrivate access

Jordan approved your request

Join to see the service details

Your approval stays tied to your email. Sign in if you already have an account, or create one to become Jordan’s service member.

Approved emailalex@example.com · verified
Create account and continue
I already have an account
After identity is confirmed, link this approval to the account, create the service membership, then reveal only this service’s private details.

This closes the guest journey while preserving the rule that service membership requires a network account.

Declined requestAlert depends on SMTP
Request update
—

Not approved this time

The private details remain hidden. The provider can still be contacted through the profile if that option is available.

Return to profile
The requester is emailed after decline only when SMTP is configured.

Declining updates the request status; it does not create a membership.

Provider manages membersImplemented
Photoxpedia IDWorkspace

Jordan · Service management

Members with access

Samsam@example.com
Remove access
This removes the active membership for this service. Profile contact permissions are separate.

The owner-only Members panel lists active service memberships and invokes removeServiceMember. It does not show an implemented confirmation dialog or removal email.

Member access removedRecovery proposed
Photoxpedia IDJourney state

Access to this service ended

You can no longer read this service’s private details.

Return to profile
Proposed explanation. Today the internal route returns not-found; the public page can return to the request gate without a clear removed-access state.

Membership removal is implemented, but this requester-facing explanation is not. An existing approved request row can remain after removal; do not promise a working retry path.

6 · Optional class branch

Class attendance follows service membership.

Try the other view ↗
Provider adds a sessionImplemented
Tuesday studio classProvider view

Schedule a session

Session nameTuesday evening class
StartsTuesday · 6:00 PM
EndsOptional
Add session
Creating a class listing does not collect payment. Photoxpedia service checkout is deferred.

Provider can add dated sessions from the service management screen.

Source accuracy: the current session form accepts only a name and start time. The optional end field pictured above is not implemented.

Class sessions listImplemented
Photoxpedia IDJourney state

Approved class member

Tuesday studio class

Tuesday evening classTuesday · 6:00 PM
Recorded attendance3 members
Check in
The current list renders a Check in button for active members. The server validates the permitted time window.

The authenticated class page lists sessions and attendance counts. This intermediate screen connects session creation to member self check-in.

Member self check-inImplemented
My membershipsToday

Tuesday evening class

Check in when you arrive

Check-in is open from 30 minutes before the session until 30 minutes after it ends.

Check in
Only a signed-in service member can self check in. A host scanning a printed card or QR code is not available.

Attendance is recorded once per user and session. There is no host scan screen in the app.

Check-in recordedFeedback proposed
Photoxpedia IDJourney state
✓

You’re checked in

SessionTuesday evening class
Recording attendance once is implemented. This explicit member confirmation is proposed; the current page only refreshes and the attendance total changes.

checkInToServiceSession inserts attendance with onConflictDoNothing. The route does not render a per-member checked-in indicator or disable repeat submission.

Outside the check-in windowFeedback proposed
Photoxpedia IDJourney state

Check-in is not open

Check in from 30 minutes before the session until 30 minutes after it ends.

With no stored end time, the helper assumes a two-hour session. An out-of-window submission currently returns silently; this feedback is proposed.

isWithinCheckInWindow enforces the server-side window. The current session form supplies only a start time; no end-time control is implemented.