Keep options clear. Check the right dates.

Options and availability in Posa’s model and talent agency software are designed around the question behind every hold: who can do this job, on these dates, and what still needs an answer?

Explore the workflow design below. The agency software is in private preview.

The options deskFictional campaign · workflow design

Juniper studio campaign

Two talent · London · work hours to agree

Booking not confirmed
Same people. Different dates. Each needs its own answer.
TalentThu 12 Nov 2026Fri 13 Nov 2026
Maya EllisAvailable replyFor 12 November onlyCheck againNew date proposed
Nia JamesNo reply yetFollow-up neededCheck againNew date proposed
Availability reply

Maya’s answer belongs to the request.

Work requested
Juniper · 12 November
Answer recorded in this example
Available for that date
Still to agree
Hours, fees and usage
Available ≠ confirmed

A positive reply helps the booker make the next decision. It does not agree the job.

1
Juniper studio campaign

Maya’s first option · terms still to agree

2
Form editorial

Maya’s second option · review with the booker

The client moves the shoot to 13 November.The 12 November reply stays with the original date. Review both people’s availability and any competing options before moving forward.
Original illustrative options desk. Ranked options, availability replies and date-change handling are design previews; this page does not send requests or place holds.

Give every answer its proper context.

A model’s current location, a client’s preference and an availability reply answer different questions. A useful options desk keeps them distinct and shows the booker what to check next.

  1. Start with the actual workKeep the enquiry, proposed people, shoot dates, time zone and any travel together. Leave unknown hours or locations visible.
  2. Check each person’s datesAsk about the specific work period. An unanswered request stays unanswered; yesterday’s answer for another job cannot fill the gap.
  3. Review the order of optionsSee competing holds and the agreed priority. A second option needs a booker’s review before it can become a commitment.
  4. Carry reviewed details into the bookingUse current replies to inform the decision, then agree people, dates, fees and usage through a separate confirmation step.

One shoot.
Two people.
A changed Friday.

Imagine a fictional booker preparing a two-person studio campaign for Juniper. The original enquiry names Thursday 12 November 2026. The client then asks for Friday instead.

Before the change

Maya has replied that she is available for Thursday; Nia has not replied. Juniper has first option on Maya for that day, with Form editorial behind it. The booker still needs Nia’s answer and the proposed hours.

  • Keep the Thursday reply attached to Thursday.
  • Give Nia’s follow-up an owner.
  • Review a competing request rather than assuming it has disappeared.

After the change

Friday is a new question for both people. The booker needs fresh replies and a review of Friday’s commitments. The original request remains useful history, but it cannot make the revised shoot ready to confirm.

The next action is simple: check both people for 13 November, then review the latest booking details.

What if someone already said “yes” before the date changed?

Keep that answer with the date and work they actually reviewed. Ask again for the changed date, and check whether travel, hours or another hold changes the answer. A previous “available” reply must not appear as agreement to the new booking.

For Juniper, Maya’s Thursday answer does not clear Friday. Nia also needs a fresh Friday request, even though her Thursday request had no reply.

A useful design to evaluate. A clear view of today.

Posa’s private staff workspace saves linked talent, client, enquiry, package and booking drafts. Access follows agency membership, and conflicting edits need review. The richer calendar and options journey shown here remain design previews.

Workflow design

Evaluate ranked options, per-person replies and the changed-date exception. Live availability requests, calendar commitments and WhatsApp replies are still to come.

Available now

The separate free comp-card maker works in your browser without an account. It does not check availability or place options.

Bring a real question to the preview.

Use a representative job to judge the workflow. These three checks reveal more than a calendar full of coloured blocks.

Can you find the unanswered date?

Look for the person, work period and next follow-up. “No reply yet” should stay visible beside a positive reply from someone else.

Can you explain the competing hold?

Check which job has first or second option, and who needs to decide if a request changes. An option rank is useful only with its context.

Can you change the shoot safely?

Move the example by a day. The old answer should remain readable while the changed date clearly asks for fresh review.

Questions from the booking desk.

A few distinctions worth settling before an agency relies on any availability workflow.

Does an availability reply confirm the booking?

No. It answers an availability request for particular work dates. The agency still needs to review options and agree the people, dates, fees and usage before confirmation.

What happens to a second option?

The design keeps it visible as a competing request. It should not automatically become a confirmed job when another request changes. The booker needs to review priorities and the current details.

Can a WhatsApp reply update Posa today?

No live WhatsApp connection is supplied in this preview. The intended direction uses the agency’s own business account, with each reply matched to the correct request before it can affect availability.

Can we run our live agency calendar here now?

The public page illustrates the intended workflow, and the private staff workspace saves linked drafts. The calendar, ranked options and availability requests are still design previews, so this is not an operational calendar offer.