An opportunity is a card on your pipeline board. It means a guest might book — or, after they book, it is the card Yada keeps for that reservation. Cards usually belong to one guest. They can also point at a stay, a campaign or journey, and an Inbox conversation.
Yada creates most cards when a guest engages. You can also create one by hand from Opportunities or the calendar. The board is the same list that conversions, auto-close, and revenue reporting use.
The four columns
New: the card just opened. Nobody has really worked it yet. Guest Signals and cards you create yourself usually start here.
In progress: there is an active thread. Campaign and journey cards often land here once the guest has been contacted or has replied.
Won: this reservation booked. Yada counts revenue from Won cards.
Archived: the card is closed without a booking, or retired as a leftover. Older help articles may call this Lost — it is the same column.
A few older cards still show an Open status in the background. Yada places those in New or In progress so they do not disappear from the board.
How a card appears
A card is created when something says this guest is in play. Yada remembers where the card came from — campaign, journey, signal, inbound inquiry, or manual — and does not change that later, even if a different tool delivers the booking.
Campaign: a guest opens or clicks a marketing email, or replies to SMS. Yada reuses the open campaign card for that guest and campaign when one already exists.
Journey: a guest replies to a journey in a way that looks like booking intent. Yada reuses the open journey card for that guest and workflow when one already exists.
Guest Signal: you (or autopilot) send a signal. The card is tied to those dates and the listing.
Inquiry: a widget, Inbox, website chat, or PMS inquiry comes in. Yada groups the same inquiry event, or the same guest with overlapping stay dates, onto one inquiry card.
Manual: you create a card from Opportunities or a calendar block.
Silent conversion: a booking arrives and no open card can take it. Yada creates a card that is already Won so the booking still appears on the board.
How a card moves
You can drag a card between columns, or change its status from the card detail. Confirm the booking before you mark Won. Archive work that is no longer active so the board stays useful.
Yada also moves cards for you:
When a reservation is confirmed in your PMS, Yada tries to mark the matching open card Won — or creates a Won card if nothing matches.
A nightly cleanup can archive stale cards: no reply after a send (7 days by default), no activity once a card is In progress (14 days by default), or a signal whose stay dates are already in the past. Cards attached to a booked stay are left alone.
Bulk Archive closes every card you select, except cards that are already Won or Archived.
What happens when a guest books
When Hostaway, Guesty, or Calry reports a confirmed reservation, Yada records that booking once and gives credit to the last useful touch.
If this stay already has a Won card, Yada stops. The update is a repeat of a booking it already knows.
Yada looks back 90 days for a campaign, journey, or signal touch it can credit — sent, delivered, opened, clicked, or replied.
The most recent touch wins. If two products share the same moment, a signal beats a journey, and a journey beats a campaign.
Yada prefers to flip an existing open card from that same product, so reporting still shows where the work started.
If nothing matches, Yada creates a new Won card (a silent conversion) so you still see the booking.
The card keeps the product it was born as. Which message actually closed the booking is stored separately for reporting. That is why a campaign card is not rewritten into a signal card when a later signal gets the credit.
One booking, one win
A reservation should produce one Won card. That keeps pipeline revenue honest and avoids two “you won a booking” notifications for the same stay.
You can still see extra open cards for the same guest — a later campaign reply, a second journey, or an inquiry that arrived after the booking. Those leftovers are normal. Archive them if they are no longer useful. Do not drag a second card to Won for a stay that is already won; Yada will keep the original win.
Coordinate follow-up
If Deal Agent is enabled, it can own an in-progress conversation, draft or send the next reply, and pause journey drips so the guest is not contacted twice. Review any opportunity-nurture journey before you run both.
Related articles
For day-to-day board actions — filters, follow-up, and moving cards — see Follow Up With Guests in Opportunities.