All blog articles

Why chat, tasks, a knowledge base and calls live in one app

Why Syncra keeps chat, tasks, a knowledge base and calls in one app, shown on one agreement that travels from a message to a task, and what we give up for it.

An agreement almost always starts in a conversation: in a chat, on a call, in a comment. Then it has to end up in a task or a document, and that is where it usually gets lost. Someone forgot to copy it over, someone copied it wrong, or nobody can find where it was discussed.

We built Syncra so that the road from a conversation to a task is a couple of clicks and never leaves the app. Below we show which parts we put together to make that possible, and what it costs.

What is in the one app

Syncra holds the four places where a team spends its day:

  • Chat. Channels, direct messages and threads.
  • Tasks. Projects with boards and lists, subtasks, and epics, which group related tasks into a larger piece of work.
  • Knowledge base. Pages with version history, and boards to draw on.
  • Calls. A video call right from a channel or direct message, with a transcript and a summary.

Syncra also has a built-in AI assistant, the Syncra assistant. When you write to it in a direct message, it reads only what you yourself can open. When someone mentions it in a channel, it reads public channels and the conversations it was added to, but not your private channels.

An example: from one message to a page

Here is the path of one agreement, step by step, as it happens in the app.

  1. A colleague writes in a channel that the sign-in button does not work. Syncra may show a Suggested task card under that message, with a Create task button.
  2. You press the button, and the New task window opens. It has a title, a project, an assignee and a due date. You check the fields and press Create task. A Task created card appears under the message.
  3. The task has a short number, for example SYN-12. When you type that number in any message, it becomes a link. Clicking the link opens the task in a panel beside the chat. A person with no access to the project does not see the task, and for them the number stays plain text.
  4. Inside a project, tasks, epics and knowledge base pages share one sequence of numbers. So SYN-13 can be a page that describes how we fix the sign-in form, and a link to it works the same way.
  5. A day later the team discusses the fix on a call started from the same channel. When the call ends, a summary card appears in that channel, with the sections Action items and Decisions. An action item can become a task through the same task window as in step 2.

All five steps are visible in one conversation and open in one window. Nobody copies text between services or has to remember where the discussion happened.

What this gives the assistant

Because chat, tasks, pages and calls are stored in one place, the assistant does not need connections to other services to see your work. You ask it a question in a conversation, and it reads the tasks and pages it needs and answers with links to its sources. When you ask, it creates tasks and writes documents. It changes only the tasks and pages you named, and deletes only after you confirm.

What we pay for it

Each part of Syncra is simpler than a service built for that one job. We do not claim to replace all of them.

  • Tasks have no sprints, estimates, time tracking, dependencies between tasks or recurring tasks. A task has one assignee.
  • You cannot invite someone from outside the workspace to a call by link.
  • If your process depends on deep planning in a dedicated tracker, Syncra alone may not be enough.

We think what exists is enough for most small teams, and that agreements lost between separate tools cost more than missing features. We list the limits plainly so you can judge for your own team.

A team of up to five people can use Syncra for free. Terms for larger teams are on the Pricing page.