Separate urgent WordPress incidents from routine requests
A broken checkout and a new team photo can arrive in the same inbox. Treating them as the same kind of urgent work makes your queue harder to trust.
- Ask what user action is blocked and whether there is a workaround.
- Record the affected site, scope and time first observed.
- Give the incident an owner; move the cosmetic request through the normal queue.
- Tell the client when the next meaningful update will come, without inventing a resolution deadline.
A priority label is a decision about impact, not a reward for the most messages. Keep that rule consistent across clients and revisit it when new evidence arrives.
Related guide: Client portals and the task backlog.
Have a correction or a workflow we should cover? Tell the IrmaWP team.