Skip to content

Polls, decisions and more ​

Beyond plain messages, Connectdary has a few structured ways to ask, agree and follow up, so answers don't get lost in the scroll.

Polls ​

Ask a question with options and see results live.

  • A poll has 2 to 10 options. It can be single or multiple choice, anonymous, and can close at a set time.
  • Everyone in the channel votes, and results change at once for everyone.
  • Only the person who asked closes the poll. A closed poll takes no more votes.
  • With AI on, you can start from an AI-drafted poll. See AI.
  • Once a poll is closed, log the result as a decision. An open poll can't be logged.
Example: Friday or Monday?

Ana types /poll Friday or Monday? in #launch (or uses + › Poll), adds the options "Friday" and "Monday", and sends. Ben votes Monday, and everyone sees the bars move. When enough have voted, Ana closes the poll and logs "Monday" as a decision.

Checklists ​

Write a list in a message with - [ ] items and it shows checkboxes. Only the author ticks items. Everyone else sees what's done. Ticking doesn't mark the message as edited, and a checklist never becomes a task. To give someone a task, see inbox and tasks.

Decisions ​

Mark a message as a decision when the team agrees on something, such as "We launch on 12 March". Each channel keeps a decisions log. Open it from the Decisions switch in the channel header.

  • The log lists decisions newest first, grouped by day. You can filter by topic and jump to the message.
  • Deleting the message removes it from the log.
  • You can't mark decisions in an archived channel.
  • Approvals and polls can log their outcome here too.
  • With AI on, Connectdary can suggest which messages look like decisions. See AI.
Example: "We launch on 12 March"

Ana writes "We launch on 12 March" in #launch. Connectdary offers Add to Decisions log? and she accepts. In the channel header she switches from Topics to Decisions and sees it at the top, with Jump to message. A month later, Chen opens that list to check the date.

Approvals ​

Ask specific people for a yes or no on something, like a budget.

  • Pick 1 to 10 approvers, and whether Everyone or Any one of them must approve. Add a deadline if you like. A reminder goes out 2 hours before.
  • Each approver sees the request waiting in their inbox.
  • Only the people you asked can answer. They answer once, on the version they saw.
  • Once the answer is settled, later answers are refused. The outcome is logged as a decision, and you're told.
  • Approvers must be able to read the channel.
Example: sign-off on a budget

Ana opens + › Ask for approval in #leadership, picks Ben and Marco, chooses Any one, and sets a deadline of Thursday 17:00. Ben finds the request in his inbox and chooses Approve. The outcome is logged as a decision and Ana is told.

Acknowledgement requests ​

Use these for announcements everyone must confirm. Post a message and ask for acknowledgement. It shows "0 of 3 acknowledged", and it waits in Waiting on you for each person until they confirm.

  • Everyone can see who has acknowledged and who hasn't.
  • You can remind the people who haven't. Only you, the sender, can.
  • Someone can take their acknowledgement back for 5 minutes. After that it stays.
  • If someone leaves the channel, they drop out of the count.
  • Notes to yourself can't ask for acknowledgement.
Example: a new policy everyone must read

Marco types /ack Expense policy updated, please read in #general. It shows "0 of 3 acknowledged" and waits in Waiting on you for each person. After two days Ana hasn't confirmed, so Marco sends a reminder. Chen takes his acknowledgement back within 5 minutes, then confirms again.

Check-ins ​

A check-in asks a team a question on a schedule, so you can skip the status meeting.

  • Anyone in the channel can start one. For example, "What are you working on?" every week at 9:00.
  • Everyone in the channel gets asked at 9:00 in their own time zone.
  • Answers are private. You only see your own until the run ends.
  • When the run ends, the channel gets one summary of all the answers. With AI on, it's written for you. Otherwise the answers are listed.
  • Once the summary is posted, the check-in is closed for that run.
  • Only the person who started it, or an admin, can change it. People who left the channel can't answer.
Example: Monday status without a meeting

Marco starts a weekly check-in in #engineering that asks "What are you working on?" every Monday at 9:00. Ben is asked at 9:00 where he is, Chen at 9:00 in Singapore. They answer privately. When the run ends, #engineering gets one summary of the answers.

Workflows ​

A workflow makes a channel do "when this happens, do that", so routine steps don't depend on someone remembering.

  • Triggers: a message, a form, a schedule or an approval.
  • Steps: post a message, start a topic, ask for an approval, or call a webhook.
  • A common use is a bug form. When someone submits it, a new topic starts in #engineering.
  • Fill in a form from the + menu or the Workflows tab of the channel. Required fields must be filled in.
  • Admins can pause any workflow. Other members can't pause someone else's.
  • Outgoing webhooks need the Team plan.

You can only find a channel's forms if you're in that channel.

Example: a bug form

Marco sets up a workflow in #engineering: when someone submits the bug form, start a topic. Ana opens the Workflows tab (or +), fills in the required fields and submits. A new topic with her report appears in #engineering without anyone retyping it.

Calls with an agenda ​

When you plan a call, add an agenda so it has a purpose and leaves a record.

  • Schedule the call for a future time and add up to ten agenda points. Name co-hosts if you want.
  • The agenda gets its own topic and card in the channel. Invited people get a push shortly before it starts.
  • Only the hosts change the agenda.
  • When the call ends, the notes are listed by agenda point.
  • You can also run a call in writing. Each person gets an end-of-day deadline, and the channel gets one summary.
  • You can't schedule a call in an archived channel.

For starting and joining calls, see calls.

Example: a planned review

Ana schedules "Design review" for Thursday 10:00 in #design with three agenda points and Ben as co-host. The agenda gets its own topic and card, and people are pushed shortly before it starts. After the call, the notes are listed by agenda point.

Channel brief ​

The brief is a short card at the top of every channel. It shows the purpose, the owners, links, pins and the latest decisions, so newcomers know what the channel is for.

  • Visitors read the brief before they join, when they browse channels.
  • Members see "Purpose updated" until they've looked at a changed purpose.
  • A purpose can be up to 500 characters.
  • Guests can read the brief but can't change it. An archived channel's brief stays as it was.
  • In a channel with 20 or more messages, AI can draft the purpose for you.

See channels and topics for more about channels.