Field network: partners and missions

The Field network page does two jobs at once, and that is the first thing to grasp before touching it. At the top, your book of partners: people outside your account, invited one by one at their email address. Below, the mission dispatch: what you hand them, and what you sign off when they bring their proof back. Its subtitle says as much: “B2B Field Partners, proof-gated missions and turnover proof validation.”

Invitation by email is no longer the only way to hand work to an outside worker. A person without a YStay account is added from the Team page, Field agents section, with a name and a phone number, and works from a link sent by SMS or WhatsApp: see Add a field agent without an account. Both kinds of workers sit in the same list, and a contact can later be invited to create an account: once the invitation is accepted, they join the network described here as a partner. Handing a housekeeping task to an agent without an account goes through assigning the task instead.

The path, screen by screen

1. Invite a field partner

   The Invite a Field Partner card asks for one thing only, an email address — the field carries the example partner@example.com — then Invite. Until someone has been invited, the card reads “No partner invited yet.”

   The invitation is tied to that exact address and to no other: your partner will have to accept it from a YStay account opened on the same address. It stays valid for seven days. And you cannot invite yourself: the account owner's address is refused.

   

2. Publish a mission from a turnover

   The Publish a mission from a turnover card lists your unfinished turnovers, one line each: the turnover number, the unit concerned and its status. The Create mission button turns one into a mission, in the Open state.

   It only appears while a turnover is still outstanding. And one turnover carries only one mission at a time: as long as that mission is neither approved nor cancelled, a second attempt is refused.

3. Assign the mission to the right partner

   Under the Missions heading, each mission sits on its own card: number and type at the top, the turnover reference below, and its state as a badge on the right.

   On an Open mission, the card adds a Partner dropdown and an Assign button. Only active partners appear there — a partner who was invited but has not accepted is not offered. Assigning moves the mission to Offered and alerts the partner on their phone.

   

4. Approve — or reject — the proof brought back

   Once the partner has finished and submitted their proof, the mission moves to Proof to review and two buttons appear: Approve proof and Reject. They exist in that state only — before it there is nothing to review; after it the decision is made. Approve proof closes the mission as Approved; Reject flips it to Disputed.

A mission's cycle, state by state

• Open — created, nobody on it. The only state where the screen offers assignment.
• Offered — sent to a partner, who has not answered yet.
• Accepted — the partner has taken it.
• In progress — they are at work.
• Proof to review — proof is in; the ball is in your court.
• Approved — you signed off. End of the road.
• Disputed — you rejected the proof.
• Cancelled — the mission was dropped before it went anywhere.

The other mission types

A mission carries a type, shown next to its number. The model provides for four: the turnover, access (work on the lock), the incident and the session fallback. Only the turnover is open today — any other request is refused, on the grounds that only turnover missions are supported at this stage. Access missions will come when that is switched on; until then door codes are handled from the reservation, as described in Guest access codes: issuance, tracking and troubleshooting.

The contractor's side: My jobs

A contractor — a person or company with a YStay account whom you have invited — works from their own account, for you and often for other hosts. What hosts entrust to them arrives on a page of their own, My jobs: there is nothing for you to set up there, but you may have to point them to it.

1. Accept the invitation

   The invitation email leads to the Field network page of their account, which shows “Accepting the invitation…” then “Invitation accepted: you are now attached to this field team.” The invitation only works for the invited address: on another account, the page answers “This invitation is meant for another email address. Sign in with the invited account.”, and “This invitation is invalid, expired or already used. Ask the host for a new one.” when the link has been used or has expired.

   A contractor who opens the link while signed out does not have to reopen their email afterwards: YStay tells them “Sign in or create your account to accept the invitation.”, keeps the invitation in that browser tab for 30 minutes at most, then brings them back to the invitation page once they are signed in or registered — after the mandatory screens, if any: documents to accept, two-factor authentication. After that delay, or in another browser, they simply reopen the link from the email. YStay remembers that page only: no other destination is kept.

2. Read their jobs

   The My jobs entry, in the Operations group of the navigation, below Field network, only appears for someone who works for at least one account: a host who has never been invited does not see it. After an acceptance, the Field network page also offers “You work for other accounts” and a See my jobs button.

   The page shows, day by day, the tasks entrusted to them — today and the seven days that follow, as “From … to …” announces —, with the name of the account that entrusted each one as a badge. Each card gives the task type, the time slot, the estimated duration, the unit and its badges: To confirm (the task awaits their answer), Overdue (an open task from a past day) and Guest on site. With no task, the page says “No job scheduled”.

   

3. Act on a task

   Opening a card shows the detail: time slot, unit, address, instructions, checklist and proof. The address only appears 24 hours before the start (“The address is shown 24 hours before the job starts.”), and no guest data ever appears on the screen. The actions are those of the rest of YStay: Accept or Decline, Acknowledge, Start, Add a photo for the proof, then Finish, with an optional note for the manager. Checklist items are ticked one by one, and Finish waits until they all are — and for the photo, when the task requires one. Decline asks for a confirmation, with no reason: “The task goes back to the manager, who is notified.”

   From 24 hours before the start, the detail also carries the Property sheet that you share — access instructions, Wi-Fi details, waste sorting, special features, useful locations, handover notes, never the useful contacts — and the checklist is grouped room by room, with the reference photos, the comparison slider and the ghost overlay. Each account decides for its own units: the contractor reads the sheet of the accounts that share it, not of the others. This page needs a network: it keeps nothing offline. See Room-by-room guidance and reference photos.

   When check-in tags are on, the task detail also carries the Scan a tag button: the contractor aims at the QR code stuck in the room, or types the code printed under it, and their visit is written in the task's log (see NFC / QR tags). The Messages section opens the task's thread between them and you, each message being translated automatically into the other person's language (see Terrain: the stay plan and My day). In the list, a “1 new message” or “3 new messages” badge flags a task with unread messages; a message you write to them also rings the bell of their own space, when they have one.

   On a check-in welcome or a check-out inspection, the detail also carries the Arrival steps (or the Departure steps): the contractor confirms two of them themselves with Confirm — “Access to the unit checked” and “Guest arrival confirmed” on arrival, “Guest departure confirmed” and “Access closed” on departure —, and the others are ticked with the inspection (“Ticked with the inspection report”). On arrival, the Key handover section lets them Get the key handover signed: the guest signs on the contractor's phone, online only, and the section then says “Handover signed at …”. Finish waits for their steps — “Confirm each step to be able to finish.” — and, when the Key handover signature on arrival setting requires it, for the signature — “Have the key handover signed to be able to finish.” The details of the steps and the signature are in Run a stay: check-in and checkout, the setting in Terrain: the stay plan and My day. Finally, Blocked / SOS lets them report a blocker — a reason picked from a closed list, an optional note, which arrives in the task's messages —, online only: offline, “Offline: call your client.” Your bell then rings straight away.

   On your side, nothing changes: the contractor remains an assignee in your list, and their actions feed the task log — “Task accepted”, “Task declined” — like those of an agent without an account — including a scanned visit (“Visit scanned — Living room”), a confirmed step (“Step confirmed — Access to the unit checked”) or the signed key handover (“Key handover signed”).

4. Set their notifications

   Notification settings, at the top of the page, opens Notifications for my jobs: “Choose, account by account, how you want to hear about the tasks entrusted to you.” Each account has its card, with three categories — Task assigned, Morning digest and Evening digest — and two channels, Push and Email. The Task assigned push is on by default, which the row flags with “On by default”; it can be turned off like the others. A contractor has no Alert category, which is reserved for managers. With no account attached, the page says “No account yet”.

   This setting is personal: during a support session it stays read-only — “consent belongs to the contractor” — and nobody can change it on their behalf.

If the screen will not move

• “Unable to load field dispatch.” — reload before concluding anything: your missions could not be read.
• “Unable to invite.” — invalid address, or the account owner's own address.
• “Unable to create mission.” — that turnover already carries an open mission.
• “Action failed.” — inactive partner, or a mission whose state changed since it was displayed.

Next

• Add a field agent without an account — workers without a YStay account, who work from a personal link.
• Housekeeping and turnovers — where the turnovers you publish as missions come from.
• Guest access codes: issuance, tracking and troubleshooting — door codes, today independent of missions.
• NFC / QR tags — the rooms' QR labels, which your contractors scan to record their visit.
• Operations — every screen of the stay and its aftermath.