Skip to content

Status Summary (Chat Skill)

The Status Summary chat skill returns a plain-text overview of all active projects and their open tasks directly in the portal chat. It works on WhatsApp and email channels and responds in the same language you used to invoke it.

When invoked, the skill queries all active projects for your tenant (or a scoped subset if you are in a business-partner context) and replies with:

  • A count of active projects.
  • Per project: code, name, current status label, total open task count, and the title of the next open task.

The response is formatted for conversational channels — no tables or HTML, just structured plain text that renders well in a chat thread.

Open the portal chat panel and look for the chat menu. The skill appears as a menu button with the label:

  • English: 📊 Project status
  • Spanish: 📊 Estado del proyecto

You can also trigger it by typing a phrase such as:

  • “Project status”
  • “Show my projects”
  • “Estado del proyecto”
  • “¿Cómo va mi proyecto?”

A typical response looks like:

📊 *Active projects summary* (2)
▸ *PRJ-001* — Website Redesign
Status: Active
Open tasks: 12
Next task: TSK-045 — Finalize homepage layout
▸ *PRJ-002* — Mobile App Launch
Status: Active
Open tasks: 8
Next task: TSK-031 — Write push notification copy

In Spanish:

📊 *Resumen de proyectos activos* (2)
▸ *PRJ-001* — Rediseño del Sitio Web
Estado: Activo
Tareas abiertas: 12
Próxima tarea: TSK-045 — Finalizar diseño de página de inicio

Open tasks include those in Backlog, To Do, In Progress, and In Review status. Tasks in Done or Cancelled are not counted.

The “next task” shown per project is the most recently updated open task for that project, up to the configured limit (default 10 tasks inspected per project).

If there are no active projects, the skill replies:

  • English: There are no active projects at this time.
  • Spanish: No hay proyectos activos en este momento.

Scoping Behavior (Business-Partner Context)

Section titled “Scoping Behavior (Business-Partner Context)”

The skill automatically scopes results based on whether you are in a business-partner (BP) context when you invoke it.

graph TD
    A[User invokes skill] --> B{BP context present?}
    B -- No --> C[Return all active tenant projects]
    B -- Yes --> D{BP has linked projects?}
    D -- No --> E[Return: no projects linked to your company]
    D -- Yes --> F[Return only projects linked to this BP]
  • No BP context — All active projects for the tenant are included.
  • BP context with linked projects — Only projects linked to the business partner through the entity-links graph are included.
  • BP context but no linked projects — The skill replies with a “no projects linked to your company” message instead of falling back to all projects.

This scoping means that when a business-partner contact invokes the skill from a BP-linked chat session, they see only the projects relevant to their account.

RequirementDetail
Bot verificationThe contact must be verified at contact_confirmed level or higher before the skill is dispatched. Unverified contacts cannot receive project data.
Tenant membershipResults are always scoped to the authenticated tenant. Cross-tenant data is never returned.
Portal permissionNo portal-level permission scope is required for this skill. The verification level and tenant scoping are the security boundary.