I've looked through all the results on this site that have to do with pagination, but they all seem to have to do with pages/results that have static information, so I'm not sure whether pagination is even appropriate for what I'm doing.
I'm working on a type of responsive CRM system, and what I need help with is this ..
The page in question is supposed to support three primary actions for my users: 1. Filter a 'calling list' (they call people that for example signed up for an event but never showed), 2. Help them quickly change the status of the people on their guest list, or write a note as they go, and 3. Allow them to send a bulk mail/SMS to people with a certain status
The default list of people is set to 'all' and sorted by the date they came into the system (registration via webb or in the CRM by the sales person).
The issue is that if the user in question lives/works in the city, they can end up having up to a hundred or so people on their guest list, compared to people in the country, that might have a few people - and I need to cater for both these scenarios.
There will be content above and below the 'working area', so I don't want to display all the results immediately in case this content below goes unnoticed, but feel like it might affect their 'flow' if they need to click 'next' all the time (seeing as it is already quite a manual and time-consuming task).
I would like to give them the option to see everything at once, but I'm not sure if a combination of pagination and 'show all' is good/bad practice. Hope I've explained this well enough ..
What are your suggestions?