Information requests
The form on the page of courses you don't sell online, the thank you page, the Requests section and the notices to your mailbox.
06/10/2026
When a course is paid but your academy hasn't connected Stripe yet, the course page doesn't show "Buy now": it shows a button that opens a request form. Whoever fills it in lands in the Requests section and you get an email.
The course page button
The public course page picks the button by itself:
| The course | The button |
|---|---|
| Free | Enroll for free: people with an account are in at once; people without one sign up and come back enrolled, with no extra step |
| Paid, with Stripe connected and verified | Buy now (or Enroll now for instalment courses): the payment |
| Paid, without Stripe | Request information or Enroll: the request form |
You pick the label of the third case in Settings › Requests and sales. A paid course whose price isn't published yet takes requests even with Stripe connected.
This is the Aladia checkout mode: in the builder (Pricing › How it is bought) you can instead force the form even with Stripe, send people to your own external link or sell by invitation only. See How you sell a course.
The form
The form opens in a box over the course page (full screen on phones) and asks for:
- Full name and email (required);
- Phone and Message (optional); the phone has a country picker with flag and calling code and is saved in international format (+39 333 123 4567);
- consent to the processing of personal data, with your text and the link to your privacy policy (required).
For live courses the request carries the edition chosen on the page.
The form fends off spam without a captcha: a hidden field that only bots fill in, the filling time and a sending limit (5 every 10 minutes from the same address, 3 a day from the same email for the same course). Over the limit people read "try again later".
After sending
The sender lands on the thank you page of your site (/grazie): a title, a text, a summary of what they sent (name, email, course) and a button. In Settings › Requests and sales › After sending you choose:
- Thank you page: your title and text (empty: "Thank you, Mario!" and "We received your request…") and the button: See more courses, A link of your choice (text and https address) or None;
- External page: an https address on your website; the sender is taken there at once.
The summary stays only in the sender's browser: it isn't in the page address and isn't visible when sharing the link.
The confirmation to the requester
As soon as someone sends a request they get a confirmation email from your academy: your academy's name, logo and colours, the sender from your email domain if you verified it and, as Reply-To, the mailbox that receives requests: if the person replies, they write to you. Inside: a thank-you, the summary (course, edition, their message), what happens next, a Go to the course button, a link to your other courses and your contacts; no mention of Aladia. The language is the one they wrote in.
In Settings › Requests and sales › Confirmation to the requester you can turn it off and write your own What happens next (empty: “We will get back to you as soon as possible, usually within two working days.”).
The confirmation goes out once per email and course every 24 hours, and never for messages blocked as spam or over the limits.
Conversions for ads
On sending, the site sends the generate_lead event (with course_id and course_name) to the tools turned on in Settings › Integrations › Marketing: GTM and GA4, Google Ads (with the request label), Meta (Lead) and TikTok (SubmitForm); see Tracking and cookies. With an external thank you page the event fires before leaving the site. Reloading /grazie doesn't repeat it.
The Requests section
Requests live in Requests, in the sidebar (Teaching group). The Owner, the Admins and anyone with a custom role holding leads.read see them; changing them takes leads.update.
- The table has Filters (search, status, course, assignee), saved Views, Columns (phone, course, status, assignee, date, message, source) and Export CSV of the filtered rows.
- Click a row to open the request: clickable email and phone, course, message, when consent was given and with which policy.
- Status: New, Contacted, Enrolled, Lost.
- Assigned to: someone on the staff (Owner, Admin, Member). They get the request notices too.
- Internal notes: only the staff sees them; they never go out.
- Enroll in the course: enrolls the person as a Student with external payment (the same path as the enrollments API): the account is created or found from the email, the You're enrolled email goes out (set password or sign in), no revenue on Aladia. The request moves to Enrolled.
Who gets notified
For every request:
- an in-app notification to the Owner and the Admins (and the assignee), linking to the request;
- an email to the mailbox of the area chosen in Settings › Requests and sales › Who gets the requests: Administration or Teaching of the reply-to (if the area has no confirmed mailbox, the main one; with no mailboxes, the Owner). Replying to the email writes straight to the person.
Webhooks
With a webhook in Settings › Webhooks you can send requests to your CRM: the events are lead.created (new request) and lead.updated (status or assignee changed). The data holds event and lead (name, email, phone, course, status, fields, date); internal notes are left out.