Quote:
Originally Posted by carzygirls
Right, it would be a separate page and I do not care who uses the code as long as its validity terminates 3 days after being generated. That way I could send emails later on to users offering a similar deal and try and get them to pay again.
|
Can a coupon code be used more than once? Meaning can 5 different users all come in using the same coupon code during it's active peripod (3 days after generation).
Jumping back to the initial confirmation email. Right now, in your system, I am assuming that when someone signs up they are intially active. So that would have to change so that they are intially inactive and do not go to an active status until confirmation/activation.
What kind of code are we dealing with for the existing system? Do you have source code if it is encoded? N eed to know this because the easiest way to change the initial status would be modifying the join up part where the user gets written to the database. If we cannot modify the existing code then a wraparound that goes in and inactivates the record immediately after creating it would have to be written. That would be a much clunkier way to go.
Could also be that we luck out and the active status on sign up is being controlled by a default in the database and all that would have to happen would be to change that default.
As a programmer I usually will provide a lump sum quote where I can see that it will benefit both myself and my client.
I would much rather bill stuff hourly for actual time spent.
Problem is that most clients think you should work for the estimate and never go over (at least on what they are billed) which in essence is a lump sum quote. If there are lots of unknowns then the quote needs to be higher to handle them. If we can eliminate the unknowns and get to a fairly concise requirements list then we can do a much more accurate quote.