Mortar's setting and the deposit call goes unanswered

You've got a board of mortar going off and a trowel in your hand, halfway through a chimney crown or a paver bed that has to be struck before it stiffens. The phone rings. It's the lady from across town who got your number off a neighbor's new brick mailbox, ready to put money down on her backyard patio. You can't stop — wiping mortar off your hands, finding a pen, walking her through a card number while the mix sets means a ruined batch and a sloppy joint. So you let it ring. By the time you've tooled the joints and washed up, she's left a voicemail, you've called back twice, and she's already given a deposit to the next mason who picked up.

KwickPhone answers that call the second it comes in, in English, Spanish, or Chinese, and it doesn't just take a message — it takes the deposit. It tells her what your deposit terms are because you've told it (a flat hold, a percentage of the estimate, whatever you actually charge), reads back the job she described, and runs her card through a PCI-safe payment flow so the number never touches you, never sits in a voicemail, and never gets scribbled on a scrap of plywood. The job is booked and paid before you've set down your trowel, and it lands in your system with her name, the address, the work she wants, and the amount collected.

For masonry this matters more than for trades that work clean and dry. Your hands are in mortar, your timing is dictated by the mix, and your good leads come by word of mouth from people standing in front of brick or stone you laid — they call once, on impulse, and if you miss them they don't try again. A deposit isn't just cash flow; it's the thing that stops a tire-kicker from ghosting you after you've blocked out three days and ordered a pallet of pavers. Letting KwickPhone collect it at the moment of interest means you stop choosing between a clean joint and a confirmed job.