Knowledge base
Support

fylt Wren

Deliver thoughtful, organized support that feels personal at scale.

fylt Wren support table with ticket subject, client, priority, status, and latest update
Studio capture. Full-width Studio view: Wren gives the team a focused queue with ticket subject, client, priority, status, and the latest update visible together.

What it does

fylt Wren is a thoughtful support workspace for client and business conversations. It brings rich-text tickets, priorities, SLAs, ownership, and reusable reply templates into one responsive queue.

Capabilities and value

Explore the parts of fylt Wren that support a connected client workflow from the first action to the next useful handoff.

Triage client conversations with clarity

Wren organizes tickets by client, category, priority, status, owner, and latest activity in a focused support queue.

Give every incoming conversation a visible next step.

Create a thoughtful response in one place

Ticket detail supports rich-text replies, canned replies, file attachments, assignment, and status updates without leaving the conversation.

Help the team respond with context and care.

Set client expectations with service standards

Categories, priorities, first-response targets, and client update levels give the team a shared support operating model.

Create a support experience that feels organized from the first reply.

Use AI to develop a useful first reply

AI drafting and reusable canned replies help agents create an editable response that still receives the human team's final review.

Maintain responsive, high-quality communication as ticket volume grows.

See the workflow in detail

Each screen below is a full-width product capture of a distinct capability, setting, or client-facing outcome.

Configure it for your business

Studio > Support > Settings

Wren settings turn your preferred service standards and response patterns into a repeatable support experience.

  1. Categories

    List the categories clients and team members use to describe a request.

    Makes triage and reporting more consistent.

  2. First-response target

    Set the SLA hours that represent the service level your business wants to provide.

    Gives the team a clear, shared response goal.

  3. Client update level

    Choose the amount of ticket and status context that clients see in their experience.

    Creates communication that matches the relationship and service model.

  4. Canned replies

    Save the reusable responses your team can insert and tailor during a ticket reply.

    Speeds up common answers while preserving a personal final message.

Getting started

  • Set categories, priorities, and SLAs in Wren → Settings.
  • Write canned replies for your most common questions.
  • Assign a default owner so new tickets never sit unclaimed.

Key settings

  • SLA targets: first-response and resolution time targets per priority.
  • Categories: the dropdown options clients see when raising a ticket.
  • Canned replies: reusable rich-text snippets for fast responses.

Daily workflow

  • Triage new tickets each morning — assign, set priority, and reply.
  • Use canned replies for repeat questions to hit your SLA every time.
  • Close out resolved tickets so your open queue stays accurate.

What updates next

Support conversations remain associated with the client relationship, team ownership, and notification system. Contact requests from the fylt marketing site also arrive in Wren, creating one clear team queue for follow-up.

fylt AI in this workflow

Use fylt AI to create or refine canned replies and prepare thoughtful ticket responses while keeping the final message personal and in your team's control.

Make the most of it

  • Assign tickets to a Flock member so ownership is always clear.
  • Every marketing 'Contact Us' submission also arrives here as a ticket.
  • Review response-time metrics monthly — they feed the marketing site's live stats.

Connected modules

fylt Wren is wired to: