This page shows what CastTool does today, using the actual interface. The tour walks you through the website, the dashboard, the model portal and booking in a few steps. Below it, every feature has its own section.
Four chapters, one screen per step. No account needed, and nothing is saved. Use the arrow keys to move along.
What clients and applicants see: your agency website, built from your model database.
Step 1 of 4
Slider, introduction, featured models, partners, a call to apply and contact details. Each section can be switched on or off.
Every image comes from the running app, captured in the demo agency with made-up names, companies and requests. The model photos there are placeholders.
A website built from your model database. Whatever your team approves appears there, and requests from the site go straight into booking.
The gallery shows every approved model. Filters are built from what is actually on your roster, so empty categories never show up.
Every approved model has a page with photos and measurements. Visitors can download the comp card as a PDF, and it only contains approved material.
Slider, introduction, featured models, partners, a call to apply and contact details. Each section can be switched on or off and moved up or down.
Classic, Atelier and Board. You choose the logo, colours and fonts, and CastTool checks the colours for sufficient contrast. Switching designs leaves your content where it is.
Build pages such as "About us" from fixed blocks. Drafts and published versions are kept apart, and the preview shows the page in your site's design.
Upload slider images in the dashboard and put them in the order you want.
Every agency starts on a subdomain. Connect your own domain with a CNAME record, and the dashboard shows the status and DNS instructions. The subdomain then redirects permanently.
Every site gets its own sitemap, robots.txt, canonical tags and hreflang automatically, plus metadata, a link preview card and structured data for the agency and its models. The audit in the dashboard shows what is missing.
The site only goes live once the required details are filled in and a privacy page is published. Each field explains what belongs in it, and there are building blocks for the privacy policy. Your agency remains responsible for the content.
Cart, request, availability check, offer, booking and invoice in one sequence, traceable in one place.
Clients add models to a request on your website, much like an online shop. The cart is stored on the server and lasts 30 days.
The request asks for project, dates, location, usage, budget and contact details in turn. Progress is saved on the server, so reloading the page loses nothing.
For each request, models get a link by email and answer available, tentative, already booked or unavailable. Each link works once, and the answer is only saved after confirming.
Every request with its status in one list, with bulk status changes. From the detail view, your team puts together the offer.
The client opens the offer through a link: terms, message, attachments and comp cards. They accept or decline, and can say why.
Once the client accepts, your team confirms the booking. The client and models receive an email, and the request keeps every step in its history.
A confirmed booking becomes a ZUGFeRD/Factur-X invoice: a PDF with embedded data following EN 16931. Numbers run without gaps, an issued invoice never changes, and corrections go through a cancellation invoice.
Connect your own Stripe account and the invoice email includes a payment link, with the payment status shown on the invoice. Without it, clients pay by bank transfer as usual.
From application to a well-kept profile. Models work in their own portal, your team keeps the final say.
Your website has an application form with photo upload and consent checkboxes. Every application arrives in the dashboard as an inactive profile with all details and photos. The form is switched off in the demo, so the screenshot shows your team's side.
Your team opens the application, checks details and photos, and activates the profile. The application becomes the profile without retyping anything, with a portal invitation if you like.
Personal details, measurements, category and visibility. Whether a model is active and whether they appear on the website are two separate switches.
Photos per model with approval, ordering and a main image. Uploads show real progress while they run.
Upload an existing comp card as a PDF, and CastTool reads the name and measurements and suggests a profile. Anything it cannot read reliably stays empty, and your team checks before creating the profile.
With an invitation, a model gets their own portal: profile, photos, documents, calendar, requests and bookings. Changes to the profile and photos only go live after your team approves them.
Models mark each day as available, maybe or unavailable. Booked days are filled in automatically, and your team sees the next 60 days on the model's page.
Passports, residence or work permits with type and expiry date. The files are kept in private storage only. An email reminder goes out 30 days and 7 days before expiry, and on the day itself.
An A5 comp card built from approved photos and measurements, for the model and for your team. Photos follow the main image and the order set in the dashboard.
Consents from the application and the portal are stored on the server with time and version. The model sees them in the portal, your team in the log, and every version stays available word for word.
If a model is under 18, CastTool asks a parent for consent through an email link, with a record and the option to withdraw. The profile stays private by default and is never indexed by search engines. Only your team can publish it. Please check whether this process is enough for your situation; the texts involved are drafts.
Client accounts with lists, shortlists by link, and the casting office as its own workspace with castings and roles.
Your team invites clients. With an account they keep shortlists, see their requests, respond to offers and find their bookings, both on your website and in the app.
Your team puts a list together and sends it as a link. The recipient needs no account and can leave feedback on each model.
A casting office gets its own workspace with its own talent database. For each casting you add roles with requirements and keep several shortlists per role, with notes and ordering. No public website needed.
The everyday tools: overview, team, email, settings and languages.
The dashboard home counts models, applications and requests and takes you straight to each list.
Invite members by email, with owner and admin roles. Sign-in can be protected with a second factor.
Your agency name is the sender, and replies go to your address. Templates can be previewed and sent to yourself as a test, and the log shows every email, including the ones that bounced.
Sender name, reply-to address, notification recipients and blocked addresses in one place.
The website, dashboard, portal and emails are available in German and English. You choose your site's languages, translate your pages per language, and every account has its own language for the interface and emails.
Sign-in, data separation, export and API: the groundwork that keeps your data yours.
Confirm your email, create your agency or casting office and pick a subdomain. The form checks right away whether the subdomain is free.
Each agency's data is separated from everyone else's in the database itself, not just in the interface. Sign-in supports roles, password reset and a second factor, and public forms are protected against bots and floods of requests.
All of your agency's data, including original files, as a ZIP. Deletion runs on a deadline and can be undone until then.
Keys per agency with their own permissions and rate limits. The API description is generated as OpenAPI from the same rules the server uses to validate requests.
Fourteen days, no card. Once you've confirmed your email you pick your subdomain, and you decide on a plan when the trial ends.