Modules

Home

Where everyone starts.

Home shows each person their open tickets, soonest due first, what’s overdue and due this week across the company, and how each project, store, or product is doing. It’s on for every company and first in the sidebar, so it’s where Worklynq opens. See Home.

• Open, overdue, and due-this-week counts
• Needs you: my open tickets by due date
• The busiest projects, stores, or products
• Ask Worklynq, when AI Search is on

Tickets

Every piece of work, tracked from start to done.

Tickets hold everything your team works on: tasks, requests, issues, inspections, bugs. Each ticket type has its own workflow — a starting stage, up to five stages in the middle, and up to four end stages — and can run in a set order or move freely. Every end stage is marked as a success, a failure, or cancelled, so work can finish more than one way: a Change Order can end Approved, Rejected, or Withdrawn. The workflow editor draws several end stages as branches. Types can sit under one another, like a Story under an Epic or a Punch Item under a Milestone.

• Ticket types with their own stages and colors
• Several endings per type — success, failure, or cancelled
• Parent and child tickets (Epic → Story, Milestone → Punch Item)
• Assignees, priorities, due dates, comments, and attachments
• Automations on each stage: create follow-up tickets, update fields, hand the ticket to Claude or Cursor, or run an AI agent
• A library of 35 ready-made ticket types by industry

Many modules build on Tickets: Operations, Projects, Team Board, Roadmaps, Product Releases, and AI Agents.

Operations

Run every store, every day.

For work that never “finishes” — a café, a shop, a hotel, a kitchen, a site. Each store or site is an operation with its own tickets, numbered OPS-1, OPS-2, and so on across the company. The Operations calendar lays out each day’s work by time, in a column per store or per team member, with week and month views; click an empty slot to add a task, or click a task to mark it done or move it. Overdue tasks are flagged, and each ticket type keeps its own color.

• One operation per store, site, or kitchen
• Day, week, and month calendar, by store or by person
• Only the ticket types you map to operations
• A dashboard for each store
• Shifts: start, breaks, and who’s on duty, with Square clock-in
• TV screens for today’s tasks and who’s on duty
• Recurring checklists that create themselves Coming in the beta

Needs: Tickets

Projects

Every job, from kickoff to handover.

For work with a start, an end, and often a client — a job site, a renovation, a client engagement. Each project has its own tickets, milestones, and deliverables, and you choose which ticket types it uses when you create it.

• Projects with dates, milestones, and deliverables
• Linked to the customer they’re for
• Their own ticket types and tickets

Needs: Tickets

Approvals

Get a yes or no, on the record.

For requests that need sign-off before they go ahead — documents, purchases, access, time off. Each type of request has its own stages, and every request ends approved, rejected, or withdrawn. Approved document approvals mark Knowledge Center pages as Verified. Optional: it’s off until your System Admin turns it on, whatever your business type, and it doesn’t need any other module.

• Document, access, purchase, and time-off types ready to use
• Add your own types, each with its own stages
• Approved, rejected, and withdrawn endings
• How Approvals works

Team Board

See the work. Keep everyone moving.

A shared board for planning and running work: keep a backlog, move tickets across the board as they progress, and plan in sprints if your team works that way.

• Backlog planning with drag and drop
• Board view by stage
• Sprints
• Filter by person, type, or priority

Needs: Tickets

Roadmaps

Turn plans into a timeline.

Lay out what's coming over the next weeks and months and connect it to the tickets that make it happen — a product roadmap, a construction schedule, or next season's store openings.

• Initiatives on a timeline
• Linked to tickets and releases
• Progress at a glance

Needs: Tickets

Product Releases

Ship with confidence.

Your products, their versions, and each release: see what's in it and what's still blocking it, and keep release notes next to the work. Mostly used by software teams.

• Products and versions
• Release planning and readiness
• Release notes

Needs: Tickets

Dashboards & Reports

Your business at a glance — and in your inbox.

Build dashboards and reports from widgets — counts and KPIs, tickets by any field, today’s schedule, overdue work, completion, and trends — plus data from your connected tools, like Square sales, QuickBooks profit and loss, and your own software through custom apps. Keep them private, share them with a team, or with everyone, and pin one to a store, project, or product. Describe the dashboard you want and AI builds it, with a live preview before anything is saved; click Explain and AI tells you what the numbers say — using Worklynq’s own AI, or a Claude or OpenAI model your company has set up. Reports can be emailed on a schedule, with an AI summary, to each person as they see it.

• Dashboards and reports built from widgets
• Data from Square, QuickBooks, your own apps, and more
• Shared with only you, a team, or everyone
• One per store, project, or product
• AI builds and explains them — or ask your own AI app
• Scheduled reports with an AI summary

Spaces

Write it down once. Share it with the right people.

Your own My Space plus shared spaces for the company, all in one module — pick a space at the top of the page tree, with My Space first. Write documents, notes, and procedures in a rich editor, start from templates, send important documents for approval (with the Approvals module on), and archive what's out of date without losing it. Archive and Templates sit under Spaces in the sidebar while it’s open.

• My Space and shared spaces, with one space picker
• Rich editor and templates
• Verified pages, with Approvals
• Version history
• Archive that stays searchable
• Pages shared with you stay private to the people they’re shared with

Knowledge Library

The company handbook that's always current.

Curated collections of your most important documents: policies, procedures, guides, playbooks, and standards. People find answers without asking around, and AI uses the Library as trusted context.

• Policies and procedures (SOPs)
• Guides, playbooks, and standards
• Searchable by everyone
• Trusted context for AI

Needs: Spaces

AI Search

Ask a question. Get an answer, with sources.

Ask in plain language — “What's still open at the downtown store?” or “What did we decide about the supplier change?” — and get an answer drawn from your tickets, documents, and connected tools, with links back to where it came from. You only see answers from what you're allowed to see: AI Search checks your roles before it searches each source, never shows other people’s personal pages, and only searches your own Gmail if you connected it.

• Plain-language questions
• Answers with links to the source
• Respects everyone's permissions
• Across tickets, documents, and connected tools
• Assist: ask, open, or do things from a panel on every page, by voice too

AI Agents

Every AI agent working in Worklynq, in one place.

Set up agents that look things up and, when you allow it, create and update tickets and docs — as the person who runs them, never with more access. Run one yourself, on a schedule, or when a ticket reaches a stage, and choose whether it asks before making changes. The same page shows your team’s own Claude, ChatGPT, or Cursor connected to Worklynq, the Claude and Cursor coding agents that work on tickets, and an activity log of everything any agent did.

• Worklynq agents: run now, on a schedule, or from a ticket stage
• Ask before making changes, with limits on each run
• Connected agents — your own Claude, ChatGPT, or Cursor
• Coding agents: hand a ticket to Claude or Cursor and get a pull request
• Activity log of every action

Needs: Tickets

Customers

Know who you sell to.

Records for the people and businesses you sell to: contact details, address, status (lead, active, inactive), tags, an owner, and notes — plus everything they’ve bought, their subscriptions, and their orders, with total spent and last purchase. Search and filter the list, and archive customers you no longer work with.

• People and businesses
• Purchases, subscriptions, and orders
• Total spent and last purchase
• Status, tags, and owner

Order Tracking

Nobody has to ask twice.

Follow every customer order from new to completed on a board with a column per stage — New, Confirmed, In progress, Ready, On the way. Add items and prices, choose pickup, delivery, shipping, or in store, set a due time, and assign it to someone. Overdue orders are outlined in red, and every order keeps a history of who did what and when.

• Board and list, with drag and drop
• One board per store, with Square orders alongside
• Walk-in orders
• Pickup, delivery, shipping, or in store
• Due times, with overdue orders flagged
• On a TV in the store
• How Order Tracking works

Needs: Customers

Engagement

Stay in touch, and bring people back.

A history on every customer — calls, meetings, emails, and notes your team logs, plus the promo emails they were sent. Create promo emails, pick who gets them (for example, active customers who bought in the last 90 days), and send now or schedule them through your own Mailchimp account, then see opens and clicks. Save the emails you send often as templates. Only customers who agreed to promo emails get them.

• Customer history: calls, meetings, emails, notes
• Promo campaigns through your Mailchimp account
• Audiences from status, tags, and recent purchases
• Templates, test sends, and scheduling
• Opens, clicks, and unsubscribes

Needs: Customers

Social media and trends Coming in the beta

Posts, mentions, and reviews in one place, and what customers ask for, complain about, and buy over time — so you can respond quickly and spot problems early.