Lead form with alerts
Leads are saved to a database, you get a Telegram alert, and the list exports to Excel.
Add a lead form to the Contacts page of my site https://your-site.ucoz.com:
— fields: name, phone, email and a comment. Validate phone and email right in the form;
— spam protection without a captcha: a hidden field and a limit on submissions from one address;
— save every lead to a database and send me the name, phone and message in Telegram right away;
— after sending, show the visitor a clear “Thank you, we will get back to you”;
— make a page where site admins see all leads, mark them as handled and download the list for Excel.
Keep keys and passwords on the server only and never show them in the chat.
Before adding the form to the page, show me what will change in the template.
Online booking
Visitors pick a service and a free slot; you get each booking in Telegram and a weekly list.
Add online booking for services to my site https://your-site.ucoz.com.
— I will send the list of services, their duration and working hours. Store them so I can change them without touching the code.
— A visitor picks a service, a day and a free time slot and leaves a name and phone number. Never show a taken slot again, even if two people book at the same moment.
— Store bookings in a database, send me a Telegram alert and show the visitor a confirmation with the date and time.
— Give admins a page with all bookings for the week. A booking can be cancelled, and the slot becomes free again.
— Every day at 9:00 send me today’s bookings in Telegram.
The form must be easy to use on a phone. Before connecting it to the site, show me what will change in the template.
OG images for every post
Every post gets its own preview image for links in Telegram, Facebook and messengers.
Generate a separate 1200×630 OG image for every item on my site https://your-site.ucoz.com so links in Telegram, Facebook and messengers show up as neat cards.
— On the image: the item title, section, logo and the site’s brand colors. Wrap and shorten long titles neatly.
— If an item has its own picture, use it as a darkened background.
— Process new items on a schedule and refresh the image when the title changes. Process existing items once.
— Plug the image into the og:image and twitter:image meta tags in the item page template. Keep a shared image for pages without their own.
Back up the template before editing it. Then check how a link preview looks in Telegram and send me a couple of examples.
Telegram bot for your articles
The bot answers questions with links to your articles and posts new ones to your channel.
Make a Telegram bot for my site https://your-site.ucoz.com.
— Someone asks a question, the bot finds matching articles on the site and replies with up to five links and short descriptions. If nothing is found, it suggests rephrasing the question.
— The bot understands typos and different word forms.
— The bot posts new materials to my channel on its own: title, picture, a couple of lines and a link. It never posts the same item twice.
— Use published materials only, skip drafts and hidden ones.
— Refresh the article list on a schedule by yourself.
Walk me through creating the bot with @BotFather and handing you its token safely. Keep the token on the server only.
Move an old PHP script
Send the old script’s files, and the agent moves it to Server Scripts without visitors noticing.
My site https://your-site.ucoz.com still runs an old PHP script at https://your-site.ucoz.com/php/… — it [briefly, what it does: e.g. searches the site’s articles]. It is slow, and the access keys are hardcoded.
I’m attaching the script files: the script itself and everything next to it. Follow the uCoz Server Scripts Skill, the section on migrating legacy scripts.
— Change nothing at first. Figure out and show me what the script does, which page or form calls it, what data it reads and which keys it contains (don’t repeat the keys themselves).
— Move it to Server Scripts as a new program next to the old one. Don’t edit the old code.
— Ask me for a new read-only uAPI key for the site data: treat the old keys from the files as leaked.
— Compare the old and new versions on the same requests: speed and results.
— Once I confirm, switch the site to the new version with one change and a template backup, so visitors don’t notice the switch.
At the end, tell me which old keys to revoke and which old files can be deleted.
Site leads to your CRM
Every lead goes to your CRM, and if the CRM is down, it retries later.
Send every new lead from my site https://your-site.ucoz.com to our CRM [CRM name]. I’ll send API access and the field list separately.
— Map the form fields to CRM fields: name, phone, email, comment, the page the lead came from, and UTM tags if present.
— If the CRM is temporarily down, keep the lead in a queue and retry later so nothing gets lost.
— Never send the same lead twice.
— If sending fails several times in a row, send me a Telegram alert.
— Make an admin page showing which leads reached the CRM and which are still queued.
Keep the CRM key on the server only. Send a test lead and show me where to check that it arrived.