Add Login, Bookings, and Member Features
What Backend Features Are
Some websites do more than present content — they handle real business: visitors book appointments, customers leave inquiries, events collect signups, members sign in to review their own records.
None of this requires you to set up a server or write a database. In Talizen you only tell the AI what the user does and what the site should return. The AI writes the backend code for the rest.
What Lives in the Backend Panel
Whatever the AI generates lands in the Backend panel on the left of the editor, and you can open it any time:
Funcs — backend logic and API entrypoints. The code the AI writes lives here.
Database — tables and records. Bookings, signups, and leads are stored here.
Auth — website users and login state. Note these are your site's visitors, not Talizen accounts.
Env — server-side secrets and configuration.
Integrations — third-party apps such as Resend for email or Alipay for payments.
Common Use Cases
Bookings — visitors pick a service and time, get a confirmation, and you can review the bookings.
Signups — users register for an event, get warned about duplicates, and see a notice when it is full.
Leads — customers submit requirements you can review and follow up on later.
Member records — signed-in users see their own bookings, applications, downloads, favorites, or orders.
Approvals — submissions enter a pending state for you to process.
How This Differs From Forms
If you only want to collect information and read it later in the dashboard, a form is enough — no backend needed.
You need backend features once the site has to make a decision about the submission: this slot is already taken, this phone number already signed up, this record is visible only to its owner, this page requires a login.
Describe the Outcome, Not the Implementation
Do not start from how it should be built. Say what you want the site to accomplish.
| Avoid | Prefer |
|---|---|
| Create a bookings table | Add booking to the site so that after a visitor submits, I can review the bookings |
| Write a duplicate-submission check | Do not let the same phone number sign up twice, and tell the user they already signed up |
| Query the current user's records | The member center should show only the records of the signed-in user |
| Add a lead status field | Customer inquiries need these states: to follow up, contacted, won, invalid |
Prompts You Can Use Directly
Add booking to my photography site. Visitors pick a service, date, and time, and submit their name and phone number. If that slot is already booked, ask them to choose another time. After a successful submission show "Your booking is submitted, we will contact you shortly." I want to review all bookings later.
Add event registration to this page. Show a success message after submission. Do not allow the same phone number to register twice — if it happens, show "You have already registered." I want to review the attendee list later.
Turn Contact Us into a customer leads feature. After a customer submits a request, I want to review the leads on the site and mark each one as to follow up, contacted, won, or invalid.
Add "My Bookings" to the member center. A signed-in user sees only the bookings they submitted. Prompt anyone who is not signed in to log in first.
Cover These Four Points
Who acts — visitor, member, customer, administrator.
What the user does — book, register, submit a request, review records, cancel an application.
How the site responds — success message, duplicate warning, sold-out notice, login prompt.
How you use it afterwards — review the list, follow up on leads, filter by status, see only your own records.
It Is Fine for the AI to Ask Back
If your description is incomplete, the AI may ask:
Can one day hold multiple booking slots?
Is there a cap on registrations?
Do leads need a follow-up status?
Should these records be visible only to signed-in users?
That is not an error — it is the AI filling in your business flow. Start with a rough description and refine it together.
How to Check the Result
Submit once through the normal flow and confirm the success message.
Refresh or reopen the site and confirm the record is still there.
Open Backend → Database and confirm the data was really stored.
Submit a duplicate on purpose and confirm the warning matches what you expected.
If login is involved, test with a second account and confirm you cannot see other people's content.
Ask the AI to generate a "review records" or "manage records" page and confirm you can work with the data afterwards.
When You Need Login
If your feature requires a signed-in user, ask the AI to generate a login page. To let visitors sign in with an existing Google or GitHub account, configure a provider first — see Configure OAuth Login — then ask the AI to add the login UI.
In One Sentence
Just tell the AI which business process the site should handle for you. Talizen gives the site the ability to remember information, evaluate conditions, return the right message, and let you manage the results afterwards.