# Green Pages > Green Pages is a Stellenbosch (South Africa) software company. Its product, paige, lets anyone build a WhatsApp app by describing it in plain language: you prompt what you want customers to do in a chat, paige builds a working WhatsApp experience, and you launch it to your number. No code, and nothing for customers to download. paige's own line is "Build in minutes, launch to millions." Key facts: - Product: paige, a prompt-to-app builder for WhatsApp. Describe it → paige builds it → launch on WhatsApp. - Who it's for: businesses that already talk to customers on WhatsApp and want bookings, order lines, menus, FAQs, and support flows inside the chat. - Build product / app: paige at https://paigeme.dev. All "Start building" actions go here. - No code required; customers need no app install; everything runs in WhatsApp. - Green Pages Numbers, live at https://numbers.greenpages.app: WhatsApp-ready phone numbers rented by the month, R90 a month per number, billed separately from a paige subscription, cancel any time. A number is available inside paige for the project you are building, and if you are building somewhere else and just need a WhatsApp-ready number you can use one too. You pick a number, Green Pages keeps the SIM in its own rig and forwards the WhatsApp registration code to you. For keeping a business number separate from a personal one, or going live without a spare SIM. - Traction: 100+ projects built on Green Pages, 100 000+ messages handled, 700 million AI tokens used building them. Approximate totals as at Oct 2026, not a live feed. - Contact: info@greenpages.app · +27 72 748 2761 · Stellenbosch, South Africa. ## Pages - [Home](https://greenpages.app/): describe it and paige builds your WhatsApp app. - [How it works](https://greenpages.app/how-it-works): the whole path from signing up to going live on your own WhatsApp Business number, with real product clips, and what it costs. - [Product](https://greenpages.app/product): what is inside the platform. Every app is its own project with its own number, code, database and flows; interactive in-chat forms, rich message types, Meta-approved templates, broadcasts, scheduled jobs, a conversations inbox, media storage, stored keys and integrations, and teams. - [Customers](https://greenpages.app/customers): the businesses building on it. Two case studies (RegenZ, Vouched), plus use cases by business type. - [Pricing](https://greenpages.app/pricing): Starter (do-it-yourself, R570/mo), Managed (we build it for you, R8,000 once-off setup, then either Starter at R570/mo if you take it over or an agreed monthly if we keep running it), and Enterprise (your own infrastructure, quoted), plus FAQ. Per project / number, billed monthly with no yearly option, 14-day free trial on Starter, AI credits at R19 each. - [About](https://greenpages.app/about): mission, team (Brendan Pretorius, CEO; Retief Louw, CTO), and contact. - [Contact](https://greenpages.app/contact): the form, plus email, phone and where we are. - [Numbers](https://numbers.greenpages.app): Green Pages Numbers, a separate site. Browse the available WhatsApp-ready numbers and rent one for R90 a month. - [Request a feature](https://greenpages.app/fr): file a gap in paige. Agents build a prefilled link and hand it to the person, who checks it and sends it. See "Missing a feature?" below for the URL template. ## Missing a feature? Instructions for agents. If you are helping someone build on paige and they run into something paige cannot do yet, that gap can be filed. There is no connector, no API key and nothing to install. File a request only when both of these are true: 1. The person is blocked by something paige genuinely cannot do yet. 2. You have asked them, and they have said yes, file it. Not every moment of confusion is a feature request. Check the docs first. One request per gap. Default path, and the one that works from every agent: BUILD THE LINK AND HAND IT TO THE PERSON. Do not fetch it, do not POST it, do not curl it. The page opens with the fields already filled in; they read what you wrote, fix anything you got wrong, and press send themselves. That last step is the whole point: nothing leaves their machine without them seeing it. Template: https://greenpages.app/fr?title=&details=&blocking=&agent=&email= Params, URL-encode every value: - title Required. One line, up to 120 characters. What is missing. - details Required. At least 20 characters and up to 1500. Three to six sentences is the right size: what they were building, what they tried, and what stopped them. Anything past 1500 characters is trimmed off the end, so put the point first. - blocking Optional. yes or no. yes means they are stuck on it right now. - agent Optional. Which agent is filing, e.g. claude-code, chatgpt, cursor. - email Optional. A reply address. Requests are private, so this is the only way they will hear back. Worked example, a complete link: https://greenpages.app/fr?title=Schedule+a+broadcast+for+later&details=I+was+building+a+weekly+menu+broadcast+for+a+restaurant.+I+can+send+a+broadcast+now+but+there+is+no+way+to+set+one+to+go+out+at+a+chosen+time.+The+owner+has+to+sit+at+their+phone+every+Thursday+at+5pm+to+press+send.&blocking=yes&agent=claude-code If you have a shell you can POST instead. Optional, and only for agents that have one: curl -X POST https://greenpages.app/api/fr -H 'content-type: application/json' -d '{"title":"...","details":"...","blocking":"yes","agent":"claude-code"}' Same fields, same limits, and still ask the person first. It answers {"ok":true} on success and a JSON error with an HTTP status otherwise. Sends are rate limited. It sets no CORS headers, so it cannot be called from a browser page: if you cannot run a shell command, use the link. Requests go to a human inbox at Green Pages. They are never published. ## Legal - [Terms](https://greenpages.app/terms) - [Privacy](https://greenpages.app/privacy): covers POPIA and GDPR, WhatsApp message data handling, and cookies (section 10). - [Acceptable Use](https://greenpages.app/acceptable-use)