Frequently asked questions

Presly is an attendance and leave tool built into Slack and Discord. It messages each monitored member every working day to Check In and Check Out with a tap, skips weekends, holidays, and approved leave, routes multi-step leave approvals, and keeps everything in a clean web portal — with reports and exports for admins.

Yes. Presly runs in both. A person can be linked to Slack, Discord, or both, and the daily check-in DM fans out to wherever they are — the same check-in on either app. The slash commands and buttons work the same on both platforms (with two small Slack naming differences noted below).

No. Presly runs entirely inside Slack/Discord and the web portal. There is no separate app to install — you interact with buttons in your DMs and, when you need it, the portal in your browser.

On the sign-in page choose “Continue with Slack” or “Continue with Discord” and authorize with that account. Presly never asks for a password — your Slack or Discord account is your identity. You will only see the areas your role allows (employee, approver, or admin).

On each working day Presly sends you a direct message with a Check In button. Tap it to record your arrival; later, tap Check Out to close the day. You can also type /check-in and /check-out at any time — no button needed. Times are recorded to the minute in your organization’s timezone.

Presly sends a reminder if you have not checked in after a set interval. If a message fails to deliver, that delivery failure is surfaced to your administrator — a failed DM never silently marks you absent. Make sure you allow DMs from the server/workspace.

Presly does not prompt on weekends, configured holidays, or days you are on approved leave. Your working days and holidays are set by your administrator.

Your group has a check-in time and a grace window. Checking in within the grace window counts as on time; after it, the record is marked late. If you never check in by the day’s cutoff, the day is recorded as absent.

Yes. Run /attendance in chat for today’s status plus your recent working days, or open the “My attendance” calendar in the portal for a full month view with check-in/out times, holidays, and leave marked.

Open the leave form — /leave on Discord, /presly-leave on Slack, or the “My leave” page in the portal — pick a leave type and dates, and submit. Presly counts only the working days in your range (weekends and holidays are excluded automatically).

Requests follow your group’s approval flow, which can have multiple steps. Approvers act on their step from a DM button or the Approvals inbox in the portal. You can watch the status of your request at any time with /leave-status.

Your balance is your annual quota minus days used and days pending. Check it on the “My leave” page or with /leave-balance. Your administrator sets the quota.

Everyday commands: /check-in and /check-out (mark attendance), /attendance (recent status), /leave-balance and /leave-status, plus /leave to open the leave form. Run /help (Discord) or /presly-help (Slack) any time for the full list. Management commands /attendance-today and /attendance-month are available to approvers and admins.

Slack reserves /leave and /help for its own built-in commands, so on Slack those two become /presly-leave and /presly-help. Everything else is identical on both platforms.

Times are stored in UTC and displayed normalized to your organization’s timezone (WIB / Asia/Jakarta by default), resolving from your personal setting, then your group, then the system default.

Yes. Presly includes a lightweight project board with sprints. Run /ticket and describe the problem in plain English (expected vs. actual); Presly’s AI drafts a structured ticket — title, description, priority, labels — routes it to the right project, and drops it into the active sprint. You can also right-click any message and choose “Create Presly ticket” to file one from that message.

If you @-mention someone or name an assignee, Presly assigns it to them (and DMs them); otherwise it stays unassigned for the team to pick up. Every ticket is attributed to whoever filed it, and admins can see all of them on the board.

No. If the AI provider is off or unavailable, Presly still files a plain ticket from your text — nothing is lost, it just isn’t auto-enriched.

Yes. Presly has a small REST API so an assistant, script, or automation can file a ticket as you. Run /presly-token in chat to mint a personal token, then POST a ticket to the API with that token — it’s filed and attributed to your Presly account, just like one from chat. See the “Creating tickets over the API” guide or email us for details.

Use /presly-token new to mint one (you’ll see the token once — copy it immediately), /presly-token list to see your active tokens, and /presly-token revoke to disable one. You can hold up to five active tokens. Tokens are stored hashed and can be revoked any time; treat one like a password.

No. Every request is tied to a mapped user’s personal token — there is no anonymous access — and each ticket counts against that user’s normal rate limits and audit trail.

Admins and approvers get a reporting portal: a monthly summary with average check-in times, per-employee trends and punctuality, and a daily attendance board — all timezone-normalized, with charts.

Yes. Administrators can export attendance reports to CSV or XLSX from the portal via a secure, signed download link.

The portal has admin screens for members, groups and schedules, holidays, system defaults, and reports. Group timezones, check-in windows, workdays, grace, reminders, and leave quotas are all configurable there. To use Slack, sync members and map each person’s Slack ID (Members → Edit → Slack user ID).

Every mutation is recorded. Admins have an audit log (who changed what, before/after) and a DM-delivery log that defaults to failed deliveries — so a message that didn’t reach someone is visible and never quietly becomes an absence.

You can see your own records; approvers see requests routed to them; administrators see records for members they manage. Presly does not read your everyday Slack or Discord messages or track anything beyond attendance, leave, and tickets you file. See our Privacy Policy for detail.

Sign-in is via Slack/Discord OAuth (no passwords stored by Presly), API tokens are stored only as hashes, and every configuration change is audited. Your organization is the controller of its attendance data; Abersoft processes it on their behalf.

Email security@abersoft.id with details and steps to reproduce, and please hold off on public disclosure until we’ve had a chance to respond. We appreciate responsible disclosure.