Jump to content
Gov  路  Market  路  Community  路  Policies  路  Funding  路  Open Call  路  Get started

Markets/en/Portal:Model/Alerts:Model

From WikiDeal
This is the latest revision of this page; it has no approved revision.

Section 2 of the market portal model. Neutral example content: replace with market-specific alerts when instantiating.

Alerts

What an alert is

An alert is a short message the platform is intended to send when a contract needs attention. Good alerts are factual, dated, and always name the next possible step. They never shame anyone: an alert opens a conversation, it does not close one. Each market defines its own alert set from the neutral types below.

Alert types with example texts

AL1. Signature pending

  • Trigger: a contract draft has been confirmed by one party and awaits the other for more than [48h].
  • Example: "Your [Market] agreement with [Name] is ready and waiting for your signature. Nothing is binding yet. Review and sign, or propose a change."

AL2. Upcoming deadline

  • Trigger: a milestone or session starts within [24h].
  • Example: "Reminder: [obligation] is due [date, time]. If something has changed, propose an amendment now rather than after the deadline."

AL3. Payment due soon

  • Trigger: a payment date is [3 days] away.
  • Example: "The payment of [amount] to [Name] is due on [date]. If paying will be difficult, say so now: a rescheduling proposal is one click away."

AL4. Payment or milestone overdue

  • Trigger: an obligation is [X days] past due, grace period expired.
  • Example: "The payment of [amount] due on [date] has not been recorded. A reply within [Y days] keeps this between the two of you; afterwards the agreed next step applies (see your contract, clause [n])."

AL5. Amendment proposed, awaiting reply

  • Trigger: one party proposed a change and the other has not answered within [72h].
  • Example: "[Name] proposed a change to your agreement: [summary]. Accept, decline, or counter-propose. Without a reply by [date], the original terms remain in force."

AL6. Expiry and renewal window

  • Trigger: the contract ends within [2 weeks].
  • Example: "Your agreement with [Name] ends on [date]. Renew it by amendment, close it with a closing contract, or let it end."

AL7. Safety or urgent condition

  • Trigger: a party reports an unsafe or blocking condition through the emergency channel.
  • Example: "[Name] reported an urgent condition: [category]. The session is paused. Please make contact immediately; the incident is timestamped."

AL8. Dispute opened

  • Trigger: a party formally raises a dispute.
  • Example: "A dispute has been opened on your agreement with [Name]. First step: mediation. A mediator will propose a session within [48h]. All messages from now on are part of the record."

Design rules

  • Every alert names the contract, the fact, the date and the next step.
  • Escalation is gradual: friendly first, formal later, never public.
  • Alerts about money always mention the renegotiation option before any consequence.
  • Frequencies and delays in [brackets] are market parameters, set in each portal's instantiation.

See also