Other: Set up Respectly end to end

Respectly is one place to reach the people you do business with — and to prove you were allowed to. Everything in the app is one of five things:

• Contacts — the people you talk to, the consent you hold for each of them, and the pipeline stage they are at.
• Templates — reusable SMS, email and voice-call content with merge fields.
• Forms and documents — forms collect information and consent; documents (called "Agreements" in the UI) get signed.
• Sends — the wizard that puts a message, a form or a document in front of the right people, lawfully.
• Automation — workflows and sequences that do the above without you.

The Inbox is where every one of those lands afterwards, and the Dashboard is the summary. That is the whole product.

Consent is tracked per contact as a 3x2 matrix: three channels (SMS, Email, Voice) times two purposes (Informational and Marketing). A contact can be reachable by informational email and by nothing else, and Respectly will enforce exactly that.

• Informational — service messages: an appointment, a receipt, a document to sign, an update on something they asked for.
• Marketing — anything promotional. Legally much harder, and in most US states it can never be granted automatically.

Every capture attempt — granted, revoked, blocked or rejected — is written to an append-only audit log you can export as a PDF per contact.

Access is controlled by roles, and each role is a set of permissions grouped by area — Contacts, Documents, Forms, Campaigns, Inbox, Templates, Analytics, Team, Roles, Settings, Billing, Webhooks and AI. System roles cannot be deleted or renamed, but you can edit what they are allowed to do, and you can create your own.

The signup form asks for first name, work email, company name, an optional industry, and a password. Or use Continue with Google, Microsoft or Apple and you will be asked for the company name and industry straight afterwards.

Click the link in the verification email, then sign in. If it never arrives, use Resend verification email on the same screen and check spam — it comes from Respectly, not from your own sending domain, which you have not set up yet.

Confirm your email address, company name and industry, then Create Organization. You land on a short "You're all set!" screen and then the setup wizard.

New signups start a 14-day trial in a pending-card state. While in that state, opening any page sends you back to the plan step. Add a card there and the whole app unlocks; the trial days are not lost by adding a card early.

The wizard runs full-screen with a step list on the left, a progress bar, and a "Finish setup later" link. Progress saves on every change, so closing the browser costs you nothing and a banner on the dashboard brings you back.

1. Welcome — orientation only, not skippable.
2. Business Details — personal details plus an Individual/Business selector. Choose Business and fill in the org name, industry, website, EIN and billing address.
3. Branding — logo, brand colour and logo position, with a live preview of your intake form.
4. Your Goals — pick Send Campaigns, Collect Documents & eSignatures, or Explore Everything. At least one is required; it decides which later steps you are shown.
5. Import Contacts — CSV with column mapping, or Google / Outlook.
6. Communications — your email sender and whether you want a shared or dedicated phone number.
7. Choose a Plan — the card gate. Not skippable for new signups.
8. What's Next — a short feature tour.

A starter kit is a curated set of tags, a pipeline with named stages, forms, signable documents, SMS and email templates, and live workflows — all built for one industry. The wizard recommends one based on the industry you chose, and provisions it at the final step.

No kit is recommended for your industry, which is fine — every kit is editable and none of them is locked to a vertical. Browse the gallery and apply whichever is structurally closest to how you work, or skip it and build as you go through this guide.

The Use Cases page shows every kit as a walkthrough — the tags, the pipeline stages and their exit criteria, each form and document with the AI prompt that generates it, the message templates, and the workflows. Apply this kit provisions the whole set for real.

If you skip out, the dashboard shows a resume banner with the steps you have left, and the Getting Started widget tracks the practical first tasks: add a contact, create an SMS template, create an email template, create a document, build a form, invite your team.

The Profile page has separate cards, each with its own Save Changes button. Make sure the account is set to Business rather than Individual — use Switch to Business if not — and complete every field below.

Upload a logo on the Profile page — it is auto-cropped and the variants used across hosted forms, emails and signature pages are generated for you. Pick a brand colour from the six presets or enter a custom hex.

The Booking Link card holds your scheduling URL, available in templates as {{booking_link}}. The Organisation Custom Fields card lets you define your own reusable values — an office address, a licence number, a support line — each available as {{org.key}}.

The Login Methods section lists Password, Google, Microsoft and Apple. Connect or unlink each one, and set or change your password here. You cannot unlink your last remaining method — the app blocks it rather than locking you out.

The Password row in Login Methods reads Change password if you already have one, and Set password if you signed up with Google, Microsoft or Apple and have never had one. Either opens the same dialog.

Login Methods lists Password, Google, Microsoft and Apple. Each provider row shows either Connect, or the linked email address and an Unlink button. Connect sends you to the provider's consent screen and brings you back with the account linked.

Below Personal Information sits a card that carries Switch to Business or Switch to Individual, depending on where you are now. Switching is not destructive — it changes which fields the page asks you for.

• Individual — Personal Information only: First Name, Last Name, the read-only Email Address, Phone Number and Photo.
• Business — adds Company Name, Industry, Business ID / EIN, Logo, Website and a billing address.

The billing address lives on the Business card, alongside Company Name and Business ID / EIN. The state and postal-code labels change to match the country you pick, so a Canadian address asks for a province and a postal code rather than a state and a ZIP.

Turn on Custom Email Sending and choose a provider: Gmail or Microsoft (one-click OAuth consent), Apple, or Custom SMTP where you supply host, port, username, password and the From address. Then use Send Test Email before you save.

The use-case chips — Documents, Forms, Campaigns — control which kinds of email use your custom sender. Authentication, billing and support email always comes from Respectly.

The Communications step of the setup wizard is where this is chosen. There are three routes:

1. Turn on the Custom Email Sending toggle.
2. Pick which use cases it applies to with the Documents, Forms and Campaigns chips.
3. Choose Gmail or Microsoft in the provider picker.
4. Press Connect. You are sent to the provider, you consent to send mail on your behalf, and you are returned to the page with the connected account shown.
5. Press Save Changes.

Pick Apple or Custom SMTP in the provider picker and the credential panel appears. The page shows app-password guidance for the host you have entered, because most providers will not accept your normal login password from an application.

Type a recipient address and press Send Test Email. A message with the subject "Respectly — Test Email" is sent using the configuration currently on screen, so you can test before you save rather than saving something broken and finding out later.

• Nothing arrives — check the host, port and username, and whether your provider requires an app password.
• It arrives from the wrong address — the From email is the field to correct.
• You are asked to reconnect — the OAuth connection has expired; press Connect again.

Consent is stored per contact as SMS / Email / Voice against Informational / Marketing. Each of the six cells reads Granted, Opted out, Blocked, Pending or Not captured, and carries the date, the source and the rule that produced it.

The read-only Contact Creation Defaults card shows an Allow/Block matrix for your billing country and for the global floor. The engine starts wide open and only restricts where a jurisdiction rule says so — which is why adding a contact auto-grants the cells that are allowed, and records the trail for each one.

With double opt-in on, a contact who opts in on a form is sent a confirmation link and stays pending until they click it. Consent only activates then. Turning it off records consent immediately, which is faster and weaker.

Pick a jurisdiction and a channel and the page explains, in plain language, what it takes to send compliantly there — opt-in requirements, consent checks, permitted sending times, and opt-out handling. Rules inherit global, then country, then state, with the most specific one winning.

Calling hours are platform rules evaluated per recipient against their local time — there is no quiet-hours setting for you to configure. An out-of-hours send is deferred, not dropped: the review step groups recipients into sending groups, and the inbox shows the campaign as Scheduled with a live countdown until it goes on its own.

Every evaluation is logged with its outcome — Allow, Conditional or Block — and can be expanded to show the routing path, the individual checks, and the suggested remediation. Filter by channel, purpose, decision, date, country, state, rule id or recipient, and Export CSV.

STOP on SMS, an email unsubscribe, a cleared box on a form, and an admin revoke all do the same thing: they opt the contact out across that whole channel and record it. Marketing emails automatically carry an unsubscribe link and your business mailing address.

The Policies page carries a "Run a compliance test" call to action alongside View Decisions. A test runs the same engine a real send runs, so the answer you get is the answer you would have got.

The outcome is one of three: Allow, Conditional or Block. Expand the record and it shows the routing path it took through global, country and state rules, each individual check it evaluated, the consent it auto-captured at contact creation, and the remediation that would clear a failure.

Policy Decisions opens with a stats bar — Total Evaluations, Allow, Conditional and Block — above the log itself. Narrow the log first, then export, so the file contains the evidence you were asked for and nothing else.

1. Set the Date Range to the period in question.
2. Filter by Channel, Purpose and Decision to isolate what you are proving.
3. Narrow further by Country, State, Rule ID or Source, or search for a single recipient.
4. Press Export CSV.

• CSV upload — bulk, with column mapping and duplicate handling.
• Google or Outlook — OAuth import straight from your address book.
• Manually — one at a time, from Add Contact.
• Your intake form — a public link or QR code the contact fills in themselves, which is the only door that also captures marketing consent properly.

The wizard runs Import Contacts, Map Columns, Import Options, then the import itself. Start with Download Template — matching it means the mapping step auto-completes and is skipped.

Choose Google or Outlook in the same import wizard, consent in the popup, and pick what to bring across. The consent rules are identical to a CSV import.

Custom fields are the data unique to your business — a policy number, a renewal date, a property address, a membership tier. Each becomes a merge variable available in every template, form and document.

Tags are free-form labels. Filter the contact list by them, apply them in bulk, target a send with them, and add or remove them automatically from a workflow.

A pipeline is an ordered set of stages a contact moves through. Switch the contact list to Kanban to drag contacts between stages, and note that moving to a stage is itself a workflow trigger.

Click any cell in the 3x2 matrix to open the Record consent drawer. Choose an evidence type — Uploaded document, Audio recording, Verbal with witness, Written note, or API reference — paste the exact disclosure the contact was shown, then choose Express opt-in or Written express opt-in.

The audit trail underneath records every attempt — granted, revoked, blocked, rejected — with timestamp, actor, IP and evidence. Log PDF on the contact page exports it.

Every account gets a built-in intake form, public at /collect/{slug}. In the editor you control which contact fields appear, which custom fields to include, the branding, and the consent options — SMS, email and voice, each split into informational and marketing.

Share it as a link or a QR code. The public page presents Service Notifications and Marketing Messages as two separate cards so the contact chooses each deliberately.

Select rows in Table view to reveal the bulk bar: Send Message, Send Document, Send Intake Form, Add Tag, Remove Tag, Update Consent, Export and Delete. Sending the intake form in bulk is the practical way to collect real marketing consent from a list you imported.

Export opens on the narrowest scope available — your selection, then your filter, then everything — so it never silently widens.

The Add Contact modal has four sections: Identity, Address, your custom fields, and Consent. On mobile the same modal opens from the floating add button instead of the header.

Save with Add Contact, or leave with Cancel. If your plan is already at its contact limit the button is blocked before the form opens.

• Search — the box marked "Search contacts..." above the list.
• Tag filter — a dropdown of your tags, with a Manage Tags link at the bottom of it.
• Pipeline — the pipeline selector next to it, which also drives the Kanban view.

The three combine. Whatever they leave on screen is the "filtered contacts" scope that Export and the bulk actions work against.

For a single person you already know the name of, the top bar search — "Search contacts, documents, forms..." — is faster than filtering the list.

• Table — the full list with checkboxes. The only view with row selection.
• Grid — contact cards, for browsing rather than working.
• Kanban — the pipeline board. Pick a pipeline in the selector, then drag cards between stages.

In Table view the header checkbox selects the current page of 20 rows. When the whole page is checked and more contacts match your filter, a banner offers "Select all {N} contacts matching this filter", capped at 500 — the same ceiling the bulk actions themselves enforce.

Edit Contact is a button on the contact page and an item in the Contact actions menu (the ⋮ button, top right). The modal is the same one you added the contact with — Identity, Address, custom fields, Consent — described as "Update the contact information below." Save with Save Changes.

In edit mode the Consent section is the live 3x2 matrix rather than a preview. Clicking a cell opens the same evidence drawer as the full consent screen, and those writes apply immediately — they do not wait for Save, and Cancel does not undo them. A Full history link jumps to the consent screen.

Switch the contact list to Kanban, choose a pipeline, and drag the contact card from one stage column to another. The contact page shows the same thing as a Pipeline Progress section.

To put contacts into a pipeline in the first place, select them in Table view and use the Add to Pipeline modal — pick a Pipeline and a Stage, then Add to {Pipeline}.

Respectly treats two contacts as the same person when their email matches exactly (ignoring case) or their phone digits match. The check runs on create and on import, within your account only.

Most duplicates arrive on import, and the Import Options step is where you decide what happens to them:

1. Skip duplicate rows — the default. Existing contacts are left exactly as they are.
2. Update existing contacts — the matching contact is updated from the CSV. Use this when the file is more current than the app.
3. Create duplicates anyway — really does create a second record, including for rows repeated inside the same file.

From the contact page, open the Contact actions menu (the ⋮ button, top right) and choose Delete Contact. The confirmation asks "Are you sure you want to delete {name}? This action cannot be undone."

To delete several at once, select the rows in Table view and use Delete in the bulk-action toolbar. Like every bulk action it is capped at 500 contacts per go.

Export Contacts opens from the header button or from the bulk-action toolbar, and offers up to three scopes:

The dialog opens on the narrowest scope available — your selection first, then your filter, then everything — so an export never silently widens back out. Picking All contacts while a filter or selection is live tells you that it ignores them.

The file includes name and contact information, company and address, tags, consent status, and a column per custom field. Confirm with Export {N} Contacts and the CSV downloads.

Two screens show the same matrix. The Consent preferences card on the contact page is the compact view; Manage Consents opens the full consent screen with the audit trail and the intake-link sender. The header there carries a "Jurisdiction · {code}" badge — the rules being applied to this contact.

Rows are the channels SMS, Email and Voice; columns are the purposes Informational and Marketing. Each cell reads:

Under the matrix, the Audit trail card lists every capture attempt with an "{N} entries" badge — timestamp, channel and purpose, an outcome of Granted, Revoked, Blocked, Rejected or Sent, the capture path, the rule id where one applied, the actor and IP, and a preview of the evidence. A contact with no history reads "No capture attempts recorded yet."

Click the cell you need to switch off and use the Revoke side of the drawer. A reason is required — a revoke with no reason is rejected, exactly as a grant with no evidence is. The revocation is written to the audit trail as Revoked and takes effect immediately.

The contact can also do this themselves, and those routes are the ones you should prefer: STOP to an SMS, the unsubscribe link in an email, or unticking the box on your intake form.

Selecting two or more rows reveals the bulk-action toolbar. Update Consent opens a dialog titled "Update consent for {N} contacts".

1. Pick an Action — Grant consent or Revoke consent.
2. Pick one or more Channels — SMS, Email, Voice.
3. Pick one or more Purposes — Informational, Marketing.
4. For a grant, add evidence; for a revoke, give a reason.
5. Confirm. Every combination of the channels and purposes you picked is applied to every selected contact.

Each contact still gets their own audit entry, and the confirmation summarises how many of the selected contacts were processed along with the granted, revoked and blocked cell counts. Bulk actions are capped at 500 contacts.

For one contact, use Send intake link at the top right of the consent screen. The dialog "Send intake form link" asks for Email or SMS — the channel you have no address for is disabled — confirms the destination under "Delivering to", and sends with Send link. The send is logged in the audit trail as a Sent entry.

For a list, select rows in Table view and use Send Intake Form in the bulk toolbar. "Send intake form to {N} contacts" asks how to Send via — Auto (email where there is one, otherwise SMS), Email, or SMS — and shows a preflight before anything goes out: how many will be sent, and how many will be skipped and why. Progress streams as it runs, and the results panel breaks down sent, skipped and failed with a Not sent list grouped by reason. It stays open on purpose, because the skips are the part worth reading.

The link opens your intake form with the contact's known details and current preferences already filled in, so they are reaffirming rather than starting from scratch. What they submit replaces what you held: anything they untick on a channel the form shows is turned off. Bulk sends are capped at 200 contacts per go.

When a channel is mid double opt-in, the Consent preferences card on the contact page shows a blue banner reading "Awaiting {SMS|email} confirmation from contact" with a Resend button beside it. Resend cancels the outstanding confirmation and issues a fresh one, which expires 72 hours later.

Until the contact clicks the link, the channel is not opted in — the consent cell reads Pending, not Granted.

Log PDF sits next to Manage at the bottom of the Consent preferences card on the contact page. It builds the PDF in your browser and downloads it straight away — there is no job to wait for.

The document is written to be read by someone outside the company: plain-English labels rather than internal keywords, a Permitted Message Types section, a per-channel marketing column, the contact's consent level, their opt-in and opt-out history, and any signatures on record. IP addresses appear only for actions the contact took themselves.

The Manage Custom Fields drawer has a Deleted fields section at the bottom with a Restore button on each row. Restoring returns the field to the end of the active list and puts its saved values back on every contact card.

This works because deleting a field only removes it from forms and cards. The delete confirmation, "Delete Custom Field", says so: values already saved on contacts stay stored, and the field can be brought back with them.

Filter by All / SMS / Email / Voice, by status and by category, and switch between grid and list. Each card offers Send, Edit, Archive, Duplicate and Delete.

Describe the message, pick a tone — Professional, Friendly, Casual or Urgent — and press Generate All Templates. Step 2 lets you keep the channels you want, name each one, set a category, and edit the content before saving.

SMS and email use double braces — {{first_name}} — while voice scripts use single braces. Use the variable picker rather than typing: it lists the system tags, your own contact custom fields, and your organisation fields.

Set the name, category and message. A live segment and character counter runs as you type, with a preview panel beside it. Keep to one segment where you can.

Name and categorise the template, write a Subject Line (merge tags allowed), and use the rich-text editor for the body. Advanced Options holds the preview text. The live preview toggles between Desktop and Mobile.

Set the script name, description and call type, then the script content — up to 5000 characters, with single-brace variables like {first_name}. Call Settings holds max duration, retry attempts and retry interval.

The Messages page holds every template you have. Narrow it with the channel pills — All, SMS, Email, Voice — then with the status filter (All, Active, Archived), the Category filter, and the "Search templates..." box. The grid and list toggle is remembered between visits.

The channel filter is in the URL, so /templates?filter=sms is a link you can bookmark or share. Accepted values are sms, email, voice and all.

On "Create new templates", scroll past the prompt box to the divider that reads "Or skip the AI and create one". Under it are three quick-create buttons — SMS Template, Email Template and Voice Template — each labelled "Start from blank".

Choosing one takes you straight to the review step with a single card, its editor already open, and no AI call. Fill in the name and content, then save.

Generation lands you on "Review your templates", badged "Step 2 — Review & edit". The toggle pills at the top choose which of the generated drafts you keep; turning one off hides its card and drops it from the count. The save button reads "Save {N} Template(s)" and updates as you toggle.

1. Turn off any channel you do not want to keep.
2. Edit each remaining draft inline, and give it a name, an optional description and a category.
3. Press Save {N} Template(s). Saved templates land in the library and are immediately selectable from a send.

The same three fields appear as the "Template Details" card in the standalone SMS and Email editors, so an existing template can be renamed or recategorised by opening Edit from its card in the library.

The inline editors used by the template review step and by the Send wizard carry an Insert Variable chip row above the field. It starts with a few favourites for that channel, then lists every custom field your tenant has defined, and ends with an All variables button that opens the full categorised picker.

The standalone SMS, Email and Voice editors use a variable picker instead. It lists the system tags plus your own fields, grouped as Contact Custom Fields and Organization, and inserts the namespaced form {{custom.<key>}} — though typing the bare {{<key>}} works just as well.

The voice script editor asks for a Script Name (up to 100 characters), a Description (up to 500), a Call Type and the Script Content. Call Type is a selector with three options: outbound AI, inbound hotline and three-way merge.

Script Content must be between 50 and 5000 characters and uses single-brace variables. The collapsible Call Settings (optional) section holds Max Duration in minutes, Retry Attempts and Retry Interval in hours; left alone they default to 10 minutes, 2 retries and 24 hours. Tags can be added alongside.

Every template card carries a Duplicate action. The copy is created in your own tenant with " (Copy)" appended to the name; open Edit on the copy to rename it and change the wording. Voice scripts duplicate the same way, tags included.

A template card offers Archive on an active template and Restore on an archived one, plus Delete. Archived templates drop out of the default view — switch the status filter from Active to Archived to see them again and restore the one you want.

The Send action on a template card opens the send flow with that template already chosen, so you go straight to recipients and review. The SMS and Email editors carry the same shortcut as a "Send Campaign" button, shown while you are editing an active template.

Inside the Send wizard the same templates are reachable per channel: set a channel card to Template mode and pick from the selector, or @-mention the template in the prompt box before generating.

The Forms & Documents page holds both. An Information Form gathers responses, consent or registrations through a shared link or QR code. An Agreement is sent to named people for e-signature. Chapter 9 covers agreements.

The Smart Create wizard asks what you are making, whether you have existing content, and then for a description. Create with AI builds the form; you then edit it like any other.

The palette holds content blocks — paragraph, heading, list, image, table, divider, section header, page break — and field blocks: Text, Date, Time, Select, File Upload and Signature. Click a field to set its label, whether it is required, validation, help text and width (full, half or third — half and third sit side by side and stack on mobile).

In form settings, turn on consent capture for email and SMS and write the consent text your contacts will see. That text is snapshotted with every submission as evidence.

Press Publish, then Share Form gives you three routes: a QR code to download as PNG or SVG for print, a public URL to paste anywhere, and Open Send Wizard to distribute it by email or SMS to chosen contacts.

View Submissions on the form card gives a searchable table with a date filter and CSV export. The richer dashboard — submission trends, per-field completion rates and answer distributions — lives in the Inbox under the form itself.

The editor palette holds two kinds of block. Field blocks ask the respondent for something and store an answer. Content blocks — paragraph, heading, list, image, table, divider, spacer, section header and page break — only explain, and collect nothing.

Click any field to open the Field Properties panel — on the right on desktop, a bottom sheet on mobile. Everything about that one field is set here, including deleting it.

Turn on capture email consent, capture SMS consent, or both, and write the consent text the respondent will read. Turn on only the channels this form is genuinely asking about.

On the public form these appear in a Communication Preferences section above the submit button, under your consent text: "I agree to receive email communications" and "I agree to receive SMS messages".

The page says so as well. Once a visitor has touched a consent box and ended with none selected, an amber notice appears: "You haven't selected any communication preferences. If you previously opted in, submitting this form will opt you out of every option shown above." Submit stays enabled, because that is how somebody opts out of everything.

The branding section sets the logo and where it sits, the primary colour used for accents and the submit button, and the input styling — border radius, border colour, background colour and text colour. The logo starts as the one on your profile, so most accounts need to change nothing here.

Once a form is published the editor's top-right button reads Share and opens the Share Form modal. QR Code offers a download as PNG or SVG for print. Public URL has Copy and "Open form in new tab". Send to Contacts hands the form to the Send wizard with "Open Send Wizard".

The standalone QR Code modal, reached from the form card, is the short version: "Download QR Code" and "Copy shareable link".

The link is hosted on the signing portal at /form-ndf/ followed by the form's own address; older forms sit at /form/ instead. That address is made once, from your account name, the form name and six random characters.

Open the form from the Inbox to reach its dashboard. The Public Access panel there carries a publish toggle, PUBLIC LINK with copy and open, QR CODE with generate and download, and EMBED ON WEBSITE — an iframe snippet with a Copy HTML button.

Paste the snippet into your own page wherever the form should appear. It loads the same hosted form as the public link, so branding, consent capture and submissions all behave identically.

There are two switches for the same thing. "Unpublish form" sits at the bottom of the Share Form modal, and the editor's top-right menu offers Unpublish once a form is live. The Public Access panel on the form dashboard has the same control as a toggle.

While a form is unpublished its public address stops serving it. Everything already collected stays exactly where it was, and republishing brings back the same address.

Delete, in the card's More menu, removes the form from the list and stops the public address working. It is not a hard erase — the record and its submissions are retained.

The submissions table has a contact column, the submitted values, the date, a search box, a date-range filter and pagination. Signature fields render as images rather than text. If you set the range backwards you get "Start date must be on or before the end date."

Export covers every submission, not just the page in front of you. The columns are the submission ID, the linked contact's name, email and phone, one column per field using your field labels, the IP address and the time it was submitted. A field that allows several answers is joined into one cell with commas.

Opening a form from the Inbox gives you its dashboard. Four tiles across the top: Submissions, Today, Response Rate and Linked Contacts.

Below them, Submission Trends charts the last 7, 30 or 90 days with the peak day and a daily average, and Field Insights gives a completion percentage and an answer distribution for every field.

The submissions table shows the contact, up to three fields and the submitted date, with a View that opens a side panel carrying the full responses, the device and IP, the consent given and a View Contact link. The actions menu offers Duplicate Form and Delete Form.

Choose Agreement, then either start from scratch and describe what you need, or upload an existing PDF. If you upload, you choose between keeping it as a PDF and placing fields on top, or converting it to an editable document.

In the editor, type prose directly and use the / slash menu to insert signing fields and merge tokens — Signature, Text, Date, Time, Select and File Upload, plus Date Signed, recipient tokens, your organisation tokens and your custom fields.

Click any field to open Field Properties and set its label, its assigned signer, whether it is required, validation and width.

The PDF editor shows the pages with a signers panel and tools to place signature and text fields per page. It auto-saves about every 30 seconds. Preview opens the document read-only with an Edit button to switch back.

Use the Send icon on the document card, or Request a Signature from the send screen. You pick the document, the delivery channels, and then the recipients — for a multi-signer agreement this step becomes Assign signers, one contact per role.

The signer opens a link with no login. They confirm their identity and agree to the terms, then the document renders with clickable fields, a required-field count, and a "Sign next field" button. A signature can be drawn, typed in one of four fonts, or uploaded as an image.

Complete Signing finishes it; Decline to Sign asks for a reason. They then see a confirmation and get an email with the signed document attached.

Drop a signed PDF in and you get the signer details, the certificate information and an integrity result. For the fuller picture, a document campaign in the Inbox offers Download Audit Trail PDF.

Once the PDF is uploaded you are asked one question that is hard to change later: "Keep as PDF and add fields" or "Make it editable".

"Tell us about it" is a description box with example prompt chips beneath it. Write between 10 and 2,000 characters, then press Create with AI and wait through "Building your content...". You can also pick from the prompt library instead of writing your own.

What comes back is a block-by-block preview. Read it, then either regenerate it or accept it with "Use This Document" — at which point it becomes a normal agreement you can edit like any other.

The same wizard has an Import Document mode. Drop in a PDF, Word or Excel file or an image up to 20 MB and it is read and rebuilt as an editable agreement rather than left as a flat page.

The PDF editor shows the document pages with a name field, a signers panel that starts with Signer 1, a preview toggle and Save and Send actions. Drag signature, initials, text, date and checkbox fields onto the page where each belongs.

Positions are recorded per page, so a field dropped on page three is stamped onto page three of the signed copy at that spot, whatever size screen the signer uses.

Add the parties in the signers panel, then open each field and set its assigned signer in Field Properties. Once there is more than one signer the fields are colour-coded so you can see at a glance who is being asked for what.

At send time the recipients step changes: instead of picking a list of contacts you get "Assign signers" and choose one contact per role. That happens whether you picked the agreement inside the wizard or opened it with the Send icon on its card.

The signers then go one at a time. When one finishes, the next is notified. Each of them sees the earlier signatures and answers read-only in place, with the other parties' fields locked; a signature field waiting on somebody else shows that it is awaiting another signer rather than offering a signing pad.

Preview opens the same full-screen editor Edit does, but read-only, with an Edit button to switch into editing when you find something to fix. An editable agreement opens in the inline editor; a PDF-backed one opens in the PDF editor.

In the rich-text editor, preview also fills your merge tokens with sample data, so you read the sentence as a recipient will rather than as a row of placeholders.

The copy is named "Copy of" plus the original name and starts as a draft. The content, the fields and the tags all come with it, so you rename it, change the clause that differs and send.

The Documents filter in the Inbox is the list of everything you have sent for signature. Each recipient carries a status of their own.

Opening the send itself gives you the campaign dashboard: the recipients table with each contact's consent and compliance, a compliance score, and Download Audit Trail PDF for document sends.

On the signing page, Decline to Sign opens a decline modal that will not close without a reason. The request is then recorded as declined with that reason, the time and the IP address, and the signer sees a "Request Declined" page instead of the document.

In a multi-signer agreement the whole thing pauses at that point. Nobody further down the order is asked to sign, which is the right behaviour — you do not want three parties signing something the first one rejected.

The declined link cannot be reused: once a request is signed, declined or expired it returns a completed page. Fix whatever they objected to and send the agreement again to give them a fresh link.

When the last required signature arrives, Respectly builds the signed copy. An uploaded PDF has the signature images and the answers stamped onto the original pages; an editable agreement is rendered fresh with the signatures and answers baked in. Either way your original stays exactly as you wrote it and can be sent again.

The signer then gets a confirmation email with a link to the signed document, and every owner on your account gets a "document signed" notification with a link back to it. In a multi-signer agreement those go out only once everybody has finished.

The finished document is sealed with a digital signature. In a multi-signer agreement the seal is applied to the final copy only — sealing an intermediate version and then adding another signature would break the seal it just applied.

You get a prompt box, a tone dropdown, channel pills for SMS, Email and Voice, and three shortcuts: Request a Signature, Send a Form, and Templates. A + button lets you @-mention an existing template, document, form, tag or pipeline stage.

Generate Draft produces one card per enabled channel, each switchable between Template, Compose and AI, each with an Insert Variable row and a live preview.

Under each card is a compliance strip showing the message type — Marketing, Informational or Transactional — and whether the content passes. That classification is what decides who is eligible two steps later, so check it rather than skimming it.

Each contact row shows consent badges and an eligibility indicator: "OK to send", or a specific reason such as "Missing phone for SMS & Voice" or "No consent for SMS & Email". A summary counts selected, visible and hidden.

Name the campaign — one is generated if you do not — and check the three summary rows for content, recipients and delivery. Delivery Eligibility breaks the numbers down per channel and purpose and names each excluded contact and why.

When to send groups recipients by calling-hour rules. Each group is sent now, scheduled by you, or deferred automatically. The final button reads Send Now or Schedule Campaign.

1. On the Send screen, describe the message in the prompt box.
2. Turn on the SMS channel pill. Email is on by default, so turn it off if you only want a text.
3. Press Generate Draft. With no channel selected the button stays disabled and an inline note reads "Select at least one delivery channel".
4. On "Customize your content", find the SMS card and press Edit to open the inline editor.
5. Continue to Select Recipients when the card has content.

The editor runs a live character and segment counter. A plain GSM-7 message fits 160 characters in one segment, or 153 per part once it splits. One accented or emoji character switches the whole message to UCS-2, which drops those limits to 70 and 67. The progress bar shifts from green to amber to red as you cross them.

Each card can be switched between Template, Compose and AI. Template loads a saved SMS template into the card, Compose is hand-written, and AI is the generated draft.

Email is the default channel. Describe the message, press Generate Draft, then press Edit on the Email card to open the inline editor beside a live preview.

Turn on the Voice channel pill before pressing Generate Draft. The wizard then shows a Voice Call card alongside any other channel you enabled, with the script and its estimated duration.

A script must be between 50 and 5000 characters. The editor shows a live word count and an estimated duration, calculated at 150 words per minute, so you can hear roughly how long the call will run before you send it.

The + button under the prompt box opens the resource picker. It searches your documents, forms, message templates, contacts, tags and pipeline stages, and drops the one you choose into the prompt as an @-mention.

• Mention a document and the send becomes a signature request, with that document already selected.
• Mention a form and the send becomes a form send, with that form already selected.
• Mention a message template and the matching channel card opens in Template mode.
• Mention nothing and the prompt is drafted by AI for the channels you picked.

The Tone dropdown sits beside the channel pills and offers Professional, Friendly and Casual. Professional is the default. Whatever you pick carries into the wizard along with the prompt, the channels and any recipients.

To change tone after generating, go Back to the entry screen — your prompt text is restored — pick the new tone and press Generate Draft again.

1. Press the Request a Signature shortcut below the prompt box. The wizard opens on "Set up your signature request".
2. In the TEMPLATE section — "Choose the content to send for signature" — switch between Document Templates and Voice Consent Templates, then pick the item to send.
3. Set the delivery channels the invitation goes out on.
4. Continue to recipients, then to review, and send or schedule as normal.

From Contacts, the Send Document action goes straight to this setup step with the selected contacts already filled in.

1. Press the Send a Form shortcut below the prompt box. The wizard opens on "Set up your form send".
2. In the FORM section — "Choose the form to send to recipients" — pick the form.
3. Set the delivery channels the invitation goes out on.
4. Continue to recipients, then review, then send or schedule.

You can also reach this branch by @-mentioning a form in the prompt box, which selects it for you.

Under each channel card preview sits the compliance strip. It shows a message type badge — Marketing, Informational or Transactional — and a TCPA Compliant badge when the content passes. When it fails, the badge reads Compliance Issue and the top risk is named beneath it.

The strip appears for all three source modes. Loading a template or typing by hand is classified exactly like an AI draft, because that classification is what drives recipient consent eligibility on the later steps and the message type recorded on the campaign.

When a channel shows Compliance Issue, an AI-drafted card offers a Regenerate & Fix button. It re-runs the composer from your original prompt with the flagged risks appended, then re-checks the result automatically, so the badge updates on its own.

When the selected document has more than one signer, Step 2 changes from "Who are you sending to?" to "Assign signers" — "Assign a contact to each signer role". Pick the contact who fills each role, then continue to review.

This also happens when the document was chosen outside the wizard — from a Send icon, an @-mention or a suggestion — because the wizard loads the document signer list first. If that lookup fails it falls back to treating the document as single-signer.

A channel card whose content carries a tag that will not resolve shows an amber warning banner with an Edit action. The message names the cause: "{{tag}} — this custom field was deleted. It will send as blank text." or "{{tag}} isn't a recognized merge tag. It will send as blank text." The same warning appears as a compact strip inside the inline editor while you type, and the preview renders the tag as a blank red block instead of showing the literal text.

1. Press Edit on the flagged card to open the inline editor.
2. Remove the tag, or replace it using the Insert Variable row so you only pick tags that exist.
3. Save the card. The banner clears once no unresolvable tag remains.

The WHEN TO SEND section groups your recipients into SENDING GROUPS by the calling-hour rules that apply where they are. Each group is either sent now, scheduled by you, or deferred automatically until its window opens. Expand a group to schedule a specific time for it.

1. Work through to the review step, "Ready to send".
2. Give the campaign a name, or leave it and one is generated from the form, document or template name plus the date.
3. Choose to schedule rather than send immediately, and pick the date and time. It has to be in the future.
4. Check the timezone. It defaults to the one your browser reports.
5. Press Schedule Campaign. The button reads Send Now when no schedule is set.

On success you land in the Inbox, where the campaign is listed with its scheduled status. Individual sending groups can still be given their own times in WHEN TO SEND.

The Send entry screen carries a Draft Campaigns panel. Each row shows when it was saved — "Saved {time ago}" — with a Resume button and a delete action. Resuming restores the whole wizard, including the step you were on.

Drafts save themselves as you move between steps, and again if you leave the page mid-send. They are held per user per tenant, up to 20 of them, and expire after seven days.

Filter pills — All, Campaigns, Documents, Forms, SMS, Email, Voice, Website Chat, Opt-Out and Opt-In — each carry a live count that respects your search and date filter. Selecting items reveals Archive, Read, Unread, Resend, Export and Delete.

A campaign held for calling hours shows as Scheduled with a live countdown and sends itself when the window opens. A blocked one carries a red Blocked badge; anything else needing attention reads Needs Review.

A thread shows date-grouped messages with delivery and read receipts, a contact panel with consent and assignment, and a composer with a Suggest reply button, SMS quick replies, attachments for email and a segment counter for SMS.

Open a campaign for Total Recipients, Sent, Delivered and Failed, plus Opened and Clicked for email, a delivery funnel, a compliance score, the message content as it was sent, and a recipients table with per-contact consent. Actions include Pause, Resume, Cancel, Duplicate and Resend to Failed.

The Opt-Out pill lists every withdrawal with its source. Opt-outs are applied automatically — there is nothing to process — but they are worth reading. The dashboard also carries a Recent Opt-Outs widget.

Each pill carries a count, and the count is exactly the number of rows that pill will show under your current search. If a badge and a list ever disagree, one of them is stale — reload rather than working from the number.

Type into "Search messages..." at the top of the list. The search applies to whichever pill you are on, and every pill count re-tallies against it — so the fastest way to find something you cannot place is to search first on All, then read the counts to see which kind of item it was.

A conversation opens as a full page. Messages are grouped by day, inbound on the left and outbound on the right with delivery and read receipts. Type in the composer and press Enter to send; Shift+Enter starts a new line.

• Suggest reply drafts an answer from the thread — take it with "Use this reply", or press Regenerate.
• Text conversations show a live character and segment count, and offer quick replies.
• Email conversations have an attachment button.
• Back to Inbox returns to the list; View Full Contact opens the contact record.

• Resolve is the green button in the conversation header. Once resolved it becomes Reopen.
• Assign to is in the header ⋮ menu, and Assigned is also editable in the contact panel on the right.
• Change Priority is in the same ⋮ menu — Low, Normal, High or Urgent.
• Archive Conversation is at the bottom of that menu.

The header states the mode: "The assistant is answering", "Waiting for a person", "You are in this chat" or "Ended". Below it you get the widget name, the visitor email if they gave one, how many times they have been in touch, and the page they arrived on.

While the assistant is handling it, a strip reads "The assistant is handling this. Sending a message takes it over." Sending one does exactly that — the composer placeholder changes from "Type to join this chat…" to "Reply to the visitor…". An amber banner carries the handover note from the assistant when the visitor has asked for a person.

The Delivery Funnel card walks the same numbers in order — Processing Complete, Delivered, then Opened and Clicked for email — and ends on Delivery Rate and Failure Rate. Beneath it, Compliance Score explains how the send was judged, and Message Content shows the message exactly as it went out.

The Recipients table is the per-person view: "Search recipients…", a status filter of All Status, Pending, Sent, Delivered, Failed, Opened, Clicked and Bounced, and the consent position of every contact.

• Pause Campaign — stops it where it is. Only offered while it is sending.
• Resume Campaign — picks it back up from where it paused.
• Cancel Campaign — ends it. Messages already sent stay sent.
• Duplicate Campaign — copies the setup so you can send it again.

Resend to Failed appears on the Actions menu of a campaign when there is anything to resend. It targets only the recipients whose delivery failed — nobody who already received the message gets it twice.

From the list itself, tick the rows you want and press Resend in the bulk bar. Use the Failed status filter on the Recipients table first if you want to see exactly who you are resending to.

Opening a document row slides in a panel with its Signature Progress. While anyone is still pending, a reminder button is offered — Send Reminder for a single signer, or "Remind All ({N})" when several are outstanding. The panel also records Last Reminder, so you can see whether they have already been chased.

Public Access holds the publish toggle plus three ways to share: PUBLIC LINK with copy and open buttons, QR CODE with generate and download, and EMBED ON WEBSITE with a "Copy HTML" snippet. Below that, Submission Trends charts 7, 30 or 90 days, and Field Insights shows per-question completion and answer spread.

The Submissions table has "Search contacts…", a date range, and a View on every row that opens the full answers alongside device, consent and a View Contact link. The actions menu offers Duplicate Form and Delete Form.

• Every row in the Recipients table has a Download compliance report button — one PDF for that one contact.
• Document campaigns also carry Download Audit Trail PDF on the Compliance Score card.
• A document opened from the Documents pill offers Download Audit Trail in its panel, always, regardless of status.
• Once signed, the same panel offers Download Signed for one signer, or "Download All ({N})" as a zip when there are several.

A workflow is a starting event that enrols contacts, then a sequence of steps they move through. The canonical example: a new contact is added, send a welcome text, wait two days, send a follow-up email.

• Contacts — a new contact is added; a contact agrees to receive messages; a contact unsubscribes; a contact is added to a group; a contact moves to a new stage.
• Forms & Documents — someone fills out a form (any form, or a specific one, including your built-in intake form); a document is signed, declined or opened.
• Messages — a campaign finishes; a message is delivered; an email is opened; a link is clicked; a contact replies.
• Manual — you enrol specific contacts yourself.

• Messages — send a text, an email, a document to sign, or a form to fill out.
• Timing — wait before continuing, or wait until a date.
• Logic — check a condition (branch), or end the workflow.
• Organize — add or remove a label, add to or remove from a group, move to a stage, update contact information.
• Advanced — notify another system by webhook.

Check a Condition opens a builder with one-tap common checks — signed a document, opted into SMS, opened my email, submitted a form, is at a stage, has a tag — plus a search for everything else. Add a second condition and an All / Any toggle appears, with a plain-English preview of the whole rule. Steps then go under the green If YES or red If NO arm.

Press Activate in the builder header. The workflow dashboard then shows Total Contacts, Currently Active, Completed and Dropped Out with an exit rate, a timeline, a funnel, and a searchable enrolments table.

A sequence is a linear set of sends over time, built in a simplified wizard on the same engine. You enrol contacts into it deliberately rather than waiting for a trigger.

Applying a starter kit creates and activates workflows immediately. Open each one and read it — they are ordinary workflows and you can edit, pause or delete any of them.

The shape is: someone fills out a form, wait a short while so it does not arrive in the same breath, then send them the document to sign. Build the form and the document first — the workflow can only pick from what already exists.

1. Open Workflows and press Create Workflow. Name it in the header — it starts as Untitled Workflow.
2. On the Starting event tab, under Forms & Documents, choose "Someone fills out a form".
3. In the config panel on the right, under "Which form(s)?", pick A specific form and select your intake form from the dropdown. All forms starts the workflow for any submission, which is rarely what you want here.
4. Switch to the Add a step tab. Under Timing, add "Wait Before Continuing" and set it to 5 minutes, or an hour, or whatever gap feels right.
5. Add a step again. Under Messages, add "Send a Document to Sign".
6. In its config panel, under "Which document?", select the document you want signed.
7. Press Activate in the builder header.

To add judgement to it, put a "Check a Condition" step between the wait and the send. Use the Has a tag or Is at a stage check so only the submissions you actually want to paper get the document, and hang the send off the If YES arm. Anything on the If NO arm runs for everyone else — a plain follow-up email, or nothing at all.

Choose "Manually enroll specific contacts". Nothing fires automatically — you pick the contacts from the workflow page whenever you want the workflow to run for them.

1. Build and Activate the workflow as normal.
2. Open it from the Workflows list to reach its page.
3. Press Enroll Contacts in the header.
4. In Add Recipients, search and tick the people you want, then press Add Contacts.

Wait Before Continuing asks "How long to wait?" and pauses that long before the next step runs. Wait Until a Date asks "Wait until what date and time?" and holds every contact until that single moment arrives — so a date in the past means the workflow simply continues.

1. Add the "Check a Condition" step. Its config panel opens with a Common checks row.
2. Tap one of the chips — Signed a document, Opted into SMS, Opened my email, Submitted a form, Is at a stage, Has a tag — or type into "Search checks…" for anything else.
3. Pick the specifics if the check asks for them, such as which document or which label.
4. Set the comparison. It reads as a sentence, with a Yes/No toggle, a dropdown, a number, or a "within the last [7] days" control depending on the check.
5. Press "+ Add condition" for a second check. A Match All / Any of these are true toggle appears, and a preview restates the whole rule in plain English.
6. Back on the canvas, add steps under the green "If YES →" column and the red "If NO →" column.

Steps on an arm run only for the contacts that took it, and when the arm runs out the contact carries on with whatever sits below the branch.

The config panel says it plainly: "Workflow ends here. When a contact reaches this step, they will exit the workflow. No further steps will run." Contacts who hit it are counted as Dropped Out on the workflow page.

It earns its place on the arm of a branch. Check whether they have signed, put End the Workflow on the If YES arm, and the reminders below the branch only ever reach the people who still need them.

There is no preview or simulation. The way to test is to run it for one person you control, which means building a copy that uses the Manual trigger.

1. Open the workflow menu on its card and choose Duplicate.
2. Edit the copy and change its starting event to "Manually enroll specific contacts".
3. Activate the copy, open it, press Enroll Contacts and pick yourself or a test contact.
4. Watch the contact move through "Contacts in this workflow" on the workflow page.
5. When it behaves, archive the copy and activate the real one.

A step missing its configuration carries a red "Needs setup" badge on the canvas, and Activate refuses with a "Finish setting up your steps" dialog that lists each unfinished step and jumps you to it. A workflow with no steps at all cannot be activated either.

The status tabs across the top of the Workflows list — All, Active, Draft, Paused, Archived — filter by exactly these. Pause and Resume are on each card menu and in the builder header; Archive is on the More menu of the workflow page.

Duplicate is on the menu of every workflow card, and on the More menu of a workflow page. The copy arrives as a Draft, so it enrols nobody until you open it, change what needs changing, and press Activate.

"Your workflow at a glance" redraws the steps as a timeline, and the funnel chart below it shows how many contacts reached each one. A big drop between two steps is the thing to look at; a drop right after a message step usually means the send is being skipped for people without a phone number, an email address or the right consent.

"Contacts in this workflow" lists everyone individually, with tabs for All, Active, Completed and Dropped Out, a "Search contacts…" box, and Started and Completed dates.

1. Details — give it a Sequence Name and an optional Description. The name is capped at 255 characters and shows a live count.
2. Audience — choose Everyone, By label, or Choose people. The wizard shows how many contacts the choice matches.
3. Messages — press Add Email, Add Text or Add Wait to build the run of steps, and reorder them with the arrows on each card.
4. Review — check the Name, Audience, step count and the Flow strip, then press Activate & Send. Save as Draft leaves it switched off.

Each Email or Text step offers "Write a message" or "Use a saved template". Writing inline gives you a subject and body for email, or the message text for a text, with an Insert merge tag palette and a character and segment count. A Wait step is a number plus a unit.

Open the sequence to reach its page. Enroll Contacts opens the Add Recipients picker — search, tick the people you want, and press Add Contacts. They start at the first step.

The rest of the page mirrors a workflow: Total Contacts, Currently Active, Completed and Dropped Out, "Your sequence at a glance", a funnel, and the contacts table. The header carries Edit, Pause or Activate, and a More menu with Duplicate and Archive.

Press Customize to drag widgets into order, hide the ones you do not want, and switch density between comfortable and compact. Hidden widgets stay in a panel you can restore from, and Reset returns to the default. The layout is saved per user.

• Outstanding Signatures — agreements sent and not yet signed, oldest first.
• Unread Inbox — replies waiting on a human.
• Failed Deliveries (24h) — usually a bad number or a bounced address.
• Compliance Attention — sends blocked or held, and consent that needs capturing.

Beyond those: Form Submission Trend, Average Turnaround Time, Document Signature Funnel, Consent Status, Recent Opt-Outs, Plan & Usage, and Quick Actions. Rows are links — clicking one drills through to the record it describes.

• Contacts — Export on the contact list, scoped to your selection or filter.
• Form submissions — CSV from the submissions table.
• Consent history — Log PDF on a contact.
• Compliance decisions — Export CSV from Settings > Policies > Decisions.
• Signature evidence — Download Audit Trail PDF on a document campaign.
• Invoices — Download per row in Billing history.

1. Press Customize on the dashboard. The grid switches into edit mode.
2. Hide any widget you do not want.
3. To bring one back, open the Hidden panel — it is labelled with a count — and press Show on the widget you want returned.
4. Press Done.

In edit mode widgets are draggable. Drag one into the position you want and press Done when the order looks right. The dashboard is a twelve-column grid on a wide screen and a single column on a phone, so the order you set here is exactly the order a phone reads top to bottom.

Density sits in the Customize bar and has two settings: comfortable, which is the default, and compact. Switch it, press Done, and the choice is saved with the rest of your layout.

Invite Member takes an email and a role. A seat banner shows how many of your plan's seats are used, and pending invitations can be resent or revoked. Existing members can be given a different role, deactivated or removed.

Create Role opens an editor with a name, description, colour and a permissions matrix grouped by area — Contacts, Documents, Forms, Campaigns, Inbox, Templates, Analytics, Team, Roles, Settings, Billing, Webhooks and AI.

Overview shows your plan, current period, next billing date and status, plus usage meters for SMS, emails, voice minutes, documents, form submissions, contacts, AI credits and seats. Plans handles upgrades — prorated and immediate — and downgrades, which take effect at the end of the period. Add-ons buys extra capacity. Payment manages cards.

A new account starts on a 14-day trial. While the trial is running, a countdown chip sits in the top bar reading "{N} day(s) left in trial" — or "Trial ends today" on the last day. On a wide screen it appends "· Add billing". Clicking it goes straight to Billing.

Adding a card does not shorten the trial — the remaining days are kept, and the card is only charged when the trial ends. Adding one early simply removes the gate.

The Plan & Usage widget on the dashboard mirrors the billing meters. When you reach a limit, a modal offers the next tier or an add-on; a soft limit instead warns that overage charges apply and lets you continue.

The Pending Invitations table below the members list shows Email, Role, Invited By, Sent and Expires, with Resend and Revoke on each row. An invitation is valid for seven days.

• Resend — issues the invitation email again. Use this when the first one was missed or has expired.
• Revoke — cancels the invitation. The link in the original email stops working.

The Members table lists Member, Role, Status and Last Active. Change Role on a row opens a dialog to pick a different role; the change takes effect the next time that person's session refreshes.

Both actions sit on the member's row in the Members table. Removal is not a deletion — the record is kept so the audit trail still names them as the actor on everything they did.

Role cards show each role's name, how many members hold it and how many permissions it carries. Create Role opens the editor; clicking an existing card opens the same editor titled Edit Role.

The matrix is grouped by Contacts, Documents, Forms, Campaigns, Inbox, Templates, Analytics, Team, Roles, Settings, Billing, Webhooks and AI. Start from nothing and tick what the job needs rather than starting from everything and removing.

Available Plans lists every plan as a card with its price, description and features. Your current one carries a Current Plan badge and a disabled button; the others offer Upgrade or Downgrade. A Monthly / Annual toggle sits above them, and annual is discounted by 20%.

Add-ons & Extra Resources lists what your plan can buy. Each card in Available to Purchase has a quantity stepper and a Purchase button, which opens an Add dialog showing the total before you commit.

Active Purchases above it lists what you already hold — the add-on, quantity, type, status and the date it started — with Cancel, Buy Again and, where a purchase errored, Retry.

Payment Methods lists the cards on file for subscription billing. Add Payment Method opens a secure card form from the payment provider — the card details are entered there and Respectly never sees or stores the number.

1. Add the new card first, so there is never a moment with no card on file.
2. Open the new card's menu and choose Set as Default.
3. Open the old card's menu, choose Remove, and confirm.

Each card shows its brand, the last four digits, its expiry date, and a Default badge on the one that will be charged.

Billing History sits below the Overview tab and covers all charges — subscription renewals, add-on purchases, overages and credits. The table shows Invoice #, Description, Type, Amount, Date and Status, with a Download action on each row that produces the PDF.

• Type is one of Subscription, Add-on, Overage or Credit.
• Status is one of Paid, Pending, Overdue or Cancelled.

CoWork is the assistant available anywhere in the app. Ask it in plain English to draft a template, build a form, create a workflow or find contacts, and it does the work — asking you to confirm before anything is created or sent.

Choose a category — Billing, Technical, Compliance, Account, Feature Request or Other, each showing its response SLA — then a subject, a description and up to five attachments. Replies arrive in the same thread.

1. Send your intake form to everyone you imported, so their consent is captured by them rather than assumed by you.
2. Send one small real campaign to a handful of contacts and read the campaign dashboard afterwards.
3. Open every workflow your starter kit activated and confirm you are happy with what it does.
4. Invite one colleague and check they can see what they need and nothing more.
5. Come back to this guide for any chapter you skipped — the Help icon in the top bar reopens it.

CoWork acts as you, inside your account, and never has more access than your own role does. Anything it cannot see, you cannot see either.

• Read and analyse — contacts, tags, pipelines, templates, documents, forms and their submissions, workflows, campaigns and the inbox.
• Create and update — contacts, tags, pipelines and stages; documents, forms, SMS and email templates, each generated populated rather than empty.
• Send — a document for signature, a form, your intake form to a contact, an SMS, email or voice campaign, and replies in the inbox.
• Automate — write a whole workflow as a trigger plus ordered steps, creating anything a step depends on first.

Drag a PDF onto the drop zone, or click it to browse. PDF files only, up to 50 MB. The result shows the signer details, the certificate the document was signed with, and an integrity banner telling you whether the file has been changed since signing. Verify another PDF clears it for the next one.